Step by Step Process of Migrating non-CDBs and PDBs Using ASM for File Storage
(Doc ID 1576755.1)
Last updated on AUGUST 04, 2018
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Information in this document applies to any platform.
To assist with migrating non-CDB databases, 12c container databases (CDB) and 12c pluggable databases (PDB) to a new container database when ASM is being used for storage.
This note will cover:
- Migrating a 12c non-CDB to a PDB whose container has a physical standby using 12c RMAN Active Database Duplication to copy the source files
This section should be used when you have a non-CDB that has either been created with or upgraded to Oracle Database 12c. You wish to convert this 12c non-CDB into a pluggable database.
- Migrating a 12c PDB into another CDB whose container has a physical standby using 12c RMAN Active Database Duplication to copy the source files
This section should be used when you have a PDB that you wish to unplug from one container database and plug into another container database.
- Migrating a 18.104.22.168 non-CDB using dbms_file_transfer scripts from note 1389592.1 performing full transportable export/import.
This section should be used when you want to migrate a pre-12c non-CDB directly into a PDB.
Using these methods, each will be done using incremental rollforward with minimal downtime for datafile movement.
For environments running 22.214.171.124 <patch 20464614> is required to be applied on the 12c Oracle Database homes.
All of the examples below consist of an environment of:
- Source environment
- Database is a Real Application Cluster database
- Database can be part of a Data Guard configuration, has no impact
- Database files are stored in ASM
- Destination environment
- Part of a Data Guard configuration with an Active Data Guard physical standby database in place
- Both the primary database and standby database are Real Application Cluster databases
- Database files are stored in ASM
This process assumes that files from the source database will need to be moved to a new location due to file management desires (e.g. wanting to have the files kept under the directory structure for a particular database) or that the souce and destination environments do not share storage. If the source and destination environments share storage (primary databases only), it is possble to perform plugin operations without needing to move files. The operations noted below in the Handling of Standby Databases during plugin will still need to be considered. It is possible that you may not need to move files on the primary site but will need to in order to maintain a standby database. The steps described here can be performed on both the primary and standby as the examples show, or just standby only or just primary only (if no standby exists).
If you do not wish to migrate files and your source and destination are on shared storage, you can maintain the standby database as well. Please see the following notes:
For non-DB Migration: Reusing the Source Standby Database Files When Plugging a non-CDB as a PDB into the Primary Database of a Data Guard Configuration <Document 2273304.1>
For PDB Migration: Reusing the Source Standby Database Files When Plugging a PDB into the Primary Database of a Data Guard Configuration <Document 2273829.1>
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
|Multitenant Plugin with OMF/ASM|
|Handling of Standby Databases during plugin.|
|Full Transportable and Export/Import implications|
|12c Migrate non-CDB and Convert to a PDB using 12c RMAN Active Database Duplication|
|12c Unplug/Plug PDB to new CDB using 12c RMAN Active Database Duplication|
|Data Pump Full Transportable Using Incremental Backups to Migrate a pre-12c non-CDB to 12c PDB|