Subscribe to Posts by Email

Subscriber Count

    699

Disclaimer

All information is offered in good faith and in the hope that it may be of use for educational purpose and for Database community purpose, but is not guaranteed to be correct, up to date or suitable for any particular purpose. db.geeksinsight.com accepts no liability in respect of this information or its use. This site is independent of and does not represent Oracle Corporation in any way. Oracle does not officially sponsor, approve, or endorse this site or its content and if notify any such I am happy to remove. Product and company names mentioned in this website may be the trademarks of their respective owners and published here for informational purpose only. This is my personal blog. The views expressed on these pages are mine and learnt from other blogs and bloggers and to enhance and support the DBA community and this web blog does not represent the thoughts, intentions, plans or strategies of my current employer nor the Oracle and its affiliates or any other companies. And this website does not offer or take profit for providing these content and this is purely non-profit and for educational purpose only. If you see any issues with Content and copy write issues, I am happy to remove if you notify me. Contact Geek DBA Team, via geeksinsights@gmail.com

Pages

12c Database : RMAN Enhancement : Duplicate from Active Database Enhancements

The ACTIVE DUPLICATE DATABASE option in 11g clone the source database by coping the full image of the data files to the auxiliary instance location through the network. This procedure doesn’t not required any pre backup existence to clone the database. However, in Oracle 12c, when ACTIVE DUPLICATE DATABASE is initiated, instead of sending the full image copy of the data files, RMAN first takes the backup of data files into backupsets, and these backups are transmit to the auxiliary location and will be restored/recovered subsequently. This functionality will surely reduce the overall impact on the source instance and also help fastening the cloning procedure. You have the flexibility to use backup compression, encryption option with this feature.

         RMAN> DUPLICATE TARGET DATABASE to stby2
                 FROM ACTIVE DATABASE
                 SECTION SIZE 500M
                 USING COMPRESSED BACKUPSETS;

 

In the previous releases, the cloned database will be opened automatically upon the process completion. The additional NOOPEN clause in 12c, will prevent opening database immediately after the cloning process completion. Therefore, the database will remain in MOUNT state after the procedure and you will have to manually open the database. This will be a good option to use in the following scenario: When the cloned database required additional settings, like, flash back or incremental backup settings. To avoid any startup problems To adjust the initialization parameters If this database is used for upgrade purpose, you can just start the db in UPGRADE mode to proceed with the upgrade. Here is the example how to use NOOPEN clause:

                 RMAN> DUPLICATE TARGET DATABASE to stby3
                          FROM ACTIVE DATABASE
                          SECTION SIZE 500M
                          USING COMPRESSED BACKUPSETS
                          NOOPEN;

1 comment to 12c Database : RMAN Enhancement : Duplicate from Active Database Enhancements