My Oracle Support Banner

Step by Step Process of Migrating non-CDBs and PDBs Using ASM for File Storage (Doc ID 1576755.1)

Last updated on FEBRUARY 07, 2020

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.

Purpose

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.

Scope

NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

This note will cover:

Using these methods, each will be done using incremental rollforward with minimal downtime for datafile movement.

To use these steps fixes 16347068, 16822629, 16874123 and 16888264 are required to be applied on 12c Oracle Database homes.  These fixes will be available in the 12.1.0.1 Patchset Update 2 or later and are available for 12.1.0.1 base as merge <patch 17759598>.

For environments running 12.1.0.2 <patch 20464614> is required to be applied on the 12c Oracle Database homes.

All of the examples below consist of an environment of:

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).

It is recommended to migrate files even if source and destination are on shared storage.  Using the steps below only add a short time to the outage (needed to complete the final incremental rollforward) and, by leaving the original files intact, there is a quick fallback to the previous environment if an immediate issue arises.

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> 

Details

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
Purpose
Scope
Details
 Goal
 Multitenant Plugin with OMF/ASM
 Handling of Standby Databases during plugin.
 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
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.