When you plug the same PDB many times you have to specify “AS COPY” in the syntax:
|
1 |
CREATE PLUGGABLE DATABASE ludo AS CLONE USING '/u01/app/oradata/ludo/ludo.xml'; |
Otherwise, you will get an error similar to:
|
1 2 |
ERROR at line 1: ORA-65122: Pluggable database GUID conflicts with the GUID of an existing container. |
There are case, however, where you cannot do it. For example, it the existing PDB should have been the clone, or if you are converting a copy of the same database from Non-CDB to PDB using autoupgrade (with autoupgrade you cannot modify the CREATE PLUGGABLE DATABASE statement).
In this case the solution might be to change the DBID of the existing PDB, via unplug/plug:
|
1 2 3 4 5 6 |
ALTER PLUGGABLE DATABASE vico CLOSE; ALTER PLUGGABLE DATABASE vico UNPLUG INTO '/u01/app/oradata/ludo/ludo.xml'; DROP PLUGGABLE DATABASE vico KEEP DATAFILES; CREATE PLUGGABLE DATABASE vico AS CLONE USING '/u01/app/oradata/ludo/ludo.xml' NOCOPY; ALTER PLUGGABLE DATABASE vico OPEN; ALTER PLUGGABLE DATABASE vico SAVE STATE; |
—
Ludo
The following two tabs change content below.
Latest posts by Ludovico (see all)
- When it comes to using Oracle, trust Oracle… - July 14, 2023
- Video: Where should I put the Observer in a Fast-Start Failover configuration? - November 29, 2022
- Video: The importance of Fast-Start Failover in an Oracle Data Guard configuration - November 29, 2022