My Oracle Support Banner

How to Restore - Dropped Pluggable database (PDB) in Multitenant (Doc ID 2034953.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.


How to Restore Dropped PDB in Multitenant using Auxiliary instance ( For Single Instance Database)


If a pluggable database (PDB)/datafiles are accidentally deleted, corrupted etc. the repository/metadata for the PDB still exists and it can be restored and recoverd

If a PDB is accidentally/intentionally dropped using DROP PLUGGABLE DATABASE <PDBNAME>, this will drop the PDB and remove the metadata from repository.  

Therefore, a restore of the PDB (including PDB PITR to before the dropped time) will fail with an error such as RMAN-06813: could not translate pluggable database PDBxx.  

Above error is identified as bug in Unpublished Bug 19808171 which required to apply the patch if recovery of Dropped PDB fails. 

For Details refer <Document 19809171.8>


As workaround, we can can restore/recover the dropped PDB in an 'Auxiliary' instance as Out-Place restore/recover.


Note: This note can be used as alternative method where Dropped pdb can be restored and recovered in auxiliary instance and can be plugged again in Source ( production ) database. 



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.