12c-Say goodbye to your backup when dropping your PDB

删除pdb：
SQL> drop PLUGGABLE database ZSKMSDB;

Pluggable database dropped.
SQL> show pdbs

    CON_ID CON_NAME                       OPEN MODE  RESTRICTED
---------- ------------------------------ ---------- ----------
         2 PDB$SEED                       READ ONLY  NO
         4 OSSPORTALDB                    MOUNTED
SQL>
只能全容器库恢复了：-----想当然的看问题了！！！

反复尝试恢复失败，最终发现一旦pdb drop后没法恢复的，天呢！！！
后来vpn**谷歌，发现有个老外有写到：

RMAN 12c : Say goodbye to your backup when dropping your PDB：
I was working on my presentations for IOUG Collaborate, and I came upon this strange behaviour in RMAN 12c (12.1.0.1.0) which to me, shouldn’t happen. Seems that when you do a DROP PLUGGABLE DATABASE , it is the equivalent of DROP DATABASE INCLUDING BACKUPS. This means that if you need to restore your PDB later on, you won’t have this registered – just be careful when dropping them-----------

http://www.pythian.com/blog/rman-12c-say-goodbye-to-your-backup-when-dropping-your-pdb/

他测试和我测试差不多，结论也一样：一旦pdb drop后，拿备份根本恢复不了:DROP PLUGGABLE DATABASE =DROP DATABASE INCLUDING BACKUPS.

***********************************************************

If you have a valid RMAN backups then do the following and it will work:
 1) Create a new Auxiliary instance, and do a RMAN restore for the following PDBS only : ROOT, PDB$SEED and the Dropped PDB that needs to be restored.

2) Open this newly created Auxiliary instance.

3) You should be able to see all the 3 PDB (root, pdb$seed and dropped PDB) with all the datafiles.

4) Follow the process of unplugging and then plugging in this dropped PDB from the restored auxiliary instance into the original source CDB and you should be all set.

5) Drop the Auxiliary instance now.

***********************************************************************************

 

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/13750068/viewspace-1177355/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/13750068/viewspace-1177355/