Skip to main content

TB045 PDB Failover Process Results in Non-Provisionable Snapshots





Alert Type

Data Availability


After an Oracle Data Guard switchover/failover of a database, it may be desired for the dSource to be connected to the new standby database ( or primary if it was originally connected to the primary ). If the dSource is a PDB, the recommended procedure to achieve this is to unlink the PDB from the original dSource and link the PDB to the new dSource. The process is documented here - KBA1103 Oracle Data Guard Switchover and Delphix dSources

Following this procedure may result in all subsequent snapshots reporting missing archive logs. These snapshots will not allow provisioning to the snapshot or any point in time.

This is not an indication of any fault with the Primary or Standby database itself. This issue only occurs if the dSource is a PDB/CDB.


After the role change in the source database and the attaching of the dSource to the new site location, snapshots from the PDB will not be provisionable.

Contributing Factors

The issue may occur in the following Delphix Engine Versions:

Major Release

 Sub Releases



5.0,,,,,,,,, ,,,,,


After linking a PDB to a different source database, snapshots may report missing logs, taking further snapshots does not resolve this issue. 



The options to resolve this issue are

1. Switch DataGuard environment back to the original configuration, then link the PDB back to the original CDB.

2. Unlink and rename the problem PDB, then Add PDB from environments. Note this process will create a new dSource, effectively doubling the space required on the system. If no VDBs are provisioned and it is not required, the old PDB could be deleted.

3. Leave the PDB linked to the same source database. If the database role is now a standby, the PDB may need to be placed in "open read only" mode or the database user set to "sys". 


This issue is resolved in the Delphix release.