Directly after my DOAG (German Oracle User Group) Conference presentation about “How Single-/Multitenant will change a DBA’s life” Martin Bach (Enkitec) approached me and told me about his experiences with the DROP PLUGGABLE DATABASE command and future recoverability.
Martin discovered that 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. I wasn’t aware of this and I’m glad that Martin told me about it.
See also my blog post from Jun 9, 2015:
This is the 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-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of restore command at 06/01/2015 10:10:40 RMAN-06813: could not translate pluggable database pdb2drop
Just a few weeks ago a colleague from German presales asked me if I know a more convenient way to restore a PDB once the magic command (DROP PLUGGABLE DATABASE) has been issued than recovering it into an auxiliary container database and unbplug/plug it. I haven’t.
But Nik (thanks!!!) told me that he pushed a MOS Note to being published explaining how to workaround this issue:
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
Now some will say: Hey, that’s simple and obvious. For me it wasn’t 😉 That’s why I write about it to remind myself of this workaround …