My Oracle Support Banner

Recovering Dropped User using Flashback Database (Doc ID 834824.1)

Last updated on JANUARY 17, 2023

Applies to:

Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Information in this document applies to any platform.


NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the
Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual
environments, actual persons, living or dead, is purely coincidental and not intended in any manner.

For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:

Directory Name: C:\temp



This article will cover in details steps to recover a wrongly dropped user using the Flashback database Technology.


This article is for DBA's of all experience level.


- Database Must be in Archive log mode
- Database Must be in Flashback database mode.
- Time at which user dropped should be within the db_flashback_retention_target and all the flashback and archivelogs should be available
- There should not be any NOLOGGING operation for any of the objects in that user's schema


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.