once you issued the DROP PLUGGABLE DATABASE command you can’t reuse a previously taken backup of this particular PDB anymore and recover the PDB into this existing CDB. Actually only the meta information in the controlfile or the RMAN catalog will be deleted. But archive logs and backup still persist.
This is the sample error message you’ll see when you try to recover a dropped pluggable database:
RMAN> restore pluggable database pdb2drop;
Starting restore at 01-JUN-15
using channel ORA_DISK_1
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-03002: failure of restore command at 06/01/2015 10:10:40
RMAN-06813: could not translate pluggable database pdb2drop
A more convenient way to restore a PDB once the magic command (DROP PLUGGABLE DATABASE) has been issued is recovering it into an auxiliary container database and unplug/plug it.
MOS Note explains how to workaround this issue:
MOS Note: 2034953.1
How to Restore Dropped PDB in Multitenant
In brief this MOS Note describes how to:
- Create an auxiliary container database
- Recover the backup (yes, you will have to have a backup of your container database) including this particular PDB
- Unplug the PDB after recovery has been finished and plug it back into the original CDB