Cloning a Pluggable Database from an RMAN Container Database Backup
Last updated on NOVEMBER 29, 2017
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 to 126.96.36.199 [Release 12.1]
Information in this document applies to any platform.
Expectation is that the reader is familiar with the concepts of Oracle Multitenant and Oracle Recovery Manager (RMAN) and basic terminology and functionality.
The following steps will show you how to perform a backup of a container database (CDB), including only the pieces required to migrate a subset of pluggable databases (PDB) with no disruption of application activity to the source PDBs. The backup and all datafiles contained in it will be consistent to a single point in time. Other than during the database backup, this operation requires no connection to the source CDB. The process makes use of Oracle Recovery Manager (RMAN) functionality to create the backup and create a clone of the CDB and specific PDBs within that container database. Once the CDB clone is created, the PDB(s) in the clone can be unplugged and plugged into a different CDB.
The RMAN backup can be created while the source CDB and PDB are active. Archive logs are included in the backupset to ensure that the cloned CDB can be recovered to a consistent point in time. Upon completion, the backup can be made accessible to some other heterogeneous hardware to be used for the restore process.
The RMAN DUPLICATE functionality is used to create the clone of the CDB. It uses data from the backupset to determine the consistency point for recovery and which datafiles need to be restored and which datafiles should be skipped and removed from the clone.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms