Database Reference
In-Depth Information
NAME GUID
------------------------------ --------------------------------
PDB3 E689AE04FAB51253E0431564A8C0354E
Now let's unplug the PDB:
SQL> alter pluggable database PDB3
2 unplug into '/home/oracle/PDB3.xml';
Pluggable database altered.
SQL> select name,guid from v$pdbs
2 where guid = 'E689AE04FAB51253E0431564A8C0354E';
NAME GUID
------------------------------ --------------------------------
PDB3 E689AE04FAB51253E0431564A8C0354E
SQL> !ls -l /home/oracle/PDB3.xml
-rw-r--r--. 1 oracle asmadmin 3690 Sep 17 12:12 /home/oracle/PDB3.xml
The command completed without a problem. You will notice that it has no effect on the availability of the PDB to
the CDB.
Dropping a PDB from the primary
Dropping the PDB from the primary is mentioned here only for the sake of completeness. The operation to drop a
PDB from the primary is replicated as a DDL command and executed seamlessly. Consider the following example
where PDB4 is dropped on the primary:
SQL> drop pluggable database pdb4 keep datafiles;
Pluggable database dropped.
The command is executed on the standby database as well:
2013-09-17 11:56:02.048000 +01:00
Recovery dropped temporary tablespace 'TEMP'
Recovery deleting file #22:'/u01/oradata/CDBFSDCB/PDB4/sysaux01.dbf' from controlfile.
Recovery dropped tablespace 'SYSAUX'
Recovery deleting file #21:'/u01/oradata/CDBFSDCB/PDB4/system01.dbf' from controlfile.
Recovery dropped tablespace 'SYSTEM'
2013-09-17 11:56:03.106000 +01:00
Recovery dropped pluggable database 'PDB4'
A quick check against v$pdbs on the primary and standby database reveals that the PDB is indeed gone.
Search WWH ::
Custom Search