PDB not shown on Standby after drop and recreate of PDB with same name on Primary
(Doc ID 2456325.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterInformation in this document applies to any platform.
Symptoms
1>Primary and Standby configuration
2>Customer dropped and recreated the PDB from the primary but the same PDB is not showing up in standby.
Example :-
Customer initially had a PDB TEST_PDB with con_id 6 :
SQL> show pdbs
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED READ ONLY NO
3 PDB_1 READ WRITE NO
4 PDB_2 READ WRITE NO
5 PDB_3 READ WRITE NO
6 TEST_PDB READ WRITE NO
TEST_PDB was then dropped and recreated with same name and it got assigned same con_id 6 which was before dropping the PDB :
SQL> show pdbs
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED READ ONLY NO
3 PDB_1 READ WRITE NO
4 PDB_2 READ WRITE NO
5 PDB_3 READ WRITE NO
6 TEST_PDB READ WRITE NO
++ After drop and recreate , PDB TEST_PDB with con_id 6 is not listed on standby :
SQL> show pdbs
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED READ ONLY NO
3 PDB_1 READ ONLY NO
4 PDB_2 READ ONLY NO
5 PDB_3 READ ONLY NO
But alert log of standby shows PDB creation was successful :
Alert log abstract from Standby
---------------------------------------
2018-08-15T23:37:14.516780-07:00
Recovery created pluggable database TEST_PDB
2018-08-15T23:37:15.702751-07:00
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |