My Oracle Support Banner

PDB Failover in a Data Guard environment: Using Data Guard Broker to Unplug a Single Failed PDB from a Standby Database and Plugging into a New Container or Migrate a Single PDB into a New Container (Doc ID 2088201.1)

Last updated on AUGUST 18, 2022

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Information in this document applies to any platform.

Goal

Provide a simple process for either migration of a single PDB or execution of a single PDB failover into another container database with minimal downtime to the impacted PDB and zero impact to any remaining primary PDBs in the primary CDB. The process takes advantage of new functionality added to the Data Guard broker command line interface DGMGRL.

The steps involve changes being made to 2 independent CDBs, caution must be taken to understand, validate and execute the steps documented below.

The functionality is supported in 12.1.0.2 and later Oracle RDBMS versions.  Support for managing Transparent Data Encryption (TDE) keys is available for Oracle RDBMS 19.15 and later versions through a patch.

Solution

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
Goal
Solution
 Additional Considerations
 Migration Steps
 Migration example:
 Failover Steps
 Process
 Failover example:
References

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