Reusing the Source Standby Database Files When Plugging a non-CDB as a PDB into the Primary Database of a Data Guard Configuration
(Doc ID 2273304.1)
Last updated on AUGUST 05, 2022
Applies to:Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
To plug in an existing 188.8.131.52 or later non-CDB database into a CDB as a new PDB where the current Primary and the target CDB both have standby databases and allow you to use the original Standby database’s data files to update the destination CDB’s Standby.
Always test the steps in a dev/test environment prior to using in production. Since the original files are being modified directly by the plugin on the primary and by the consumption of the files on the standby, severe errors could cause you to need to either restore the original non-CDB databases (both primary and standby) or defer recovery of the PDB at the standby and use the steps in <Document 1916648.1> to re-enable recovery.
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
|For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:|