Which three statements are true concerning unplugging a pluggable database (PDB)?

A.
The PDB must be open in read only mode.

B.
The PDB must be dosed.

C.
The unplugged PDB becomes a non-CDB.

D.
The unplugged PDB can be plugged into the same multitenant container database (CDB)

E.
The unplugged PDB can be plugged into another CDB.

F.
The PDB data files are automatically removed from disk.

Explanation:
B, not A: The PDB must be closed before unplugging it.
D: An unplugged PDB contains data dictionary tables, and some of the columns in these encode
information in an endianness-sensitive way. There is no supported way to handle the conversion
of such columns automatically. This means, quite simply, that an unplugged PDB cannot be
moved across an endianness difference.
E (not F): To exploit the new unplug/plug paradigm for patching the Oracle version most
effectively, the source and destination CDBs should share a filesystem so that the PDB’s datafiles
can remain in place.
Reference: Oracle White Paper, Oracle Multitenant

Show Hint

← Previous question

Next question →

Ziad Abuqasem

Unplug PDB from CDB :
1- connect to a CDB as common user
2- verify that PDB is opened READ ONLY
3- ALTER PLUGGABLE DATABASE PDB1 UNPLUG INTO ‘xmlfile.xml’;
4- DROP the PDB from CDB
these steps from oracle database 12c course

the CORRECT answer ADE

Emanuel camacho

BDE

To unplug a PDB, you first close it and then generate an XML manifest file. The XML file contains information about the names and the full paths of the tablespaces, as well as data files of the unplugged PDB. The information will be used by the plugging operation.

In this section, you unplug two PDBs to plug them with different methods.
Use SQL*Plus to close the PDBs before they can be unplugged. Note: The pdb2 database may not have been opened, so you may receive an error that the PDB is already closed.
. oraenv
[enter cdb1 at the prompt]

sqlplus / as sysdba
alter pluggable database pdb1 close immediate;

alter pluggable database pdb2 close immediate;

Unplug the closed PDB and then specify the path and name of the XML file.
alter pluggable database pdb1 unplug into ‘/u01/app/oracle/oradata/pdb1.xml’;

alter pluggable database pdb2 unplug into ‘/u01/app/oracle/oradata/pdb2.xml’;

Drop the closed PDB and keep the data files.
drop pluggable database pdb1 keep datafiles;

drop pluggable database pdb2 keep datafiles;

Verify the status of the unplugged PDB.
select pdb_name, status from cdb_pdbs where pdb_name in (‘PDB1’, ‘PDB2’);
[you should see no rows]
exit

The unplugging operation makes changes in the PDB data files to record that the PDB was properly and successfully unplugged. Because the PDB is still part of the CDB, you can back it up in Oracle Recovery Manager (Oracle RMAN). This backup provides a convenient way to archive the unplugged PDB. After backing it up, you then remove it from the CDB catalog. But, of course, you must preserve the data files for the subsequent plugging operation.

http://www.oracle.com/webfolder/technetwork/tutorials/obe/db/12c/r1/pdb/pdb_unplug_plug/pdb_unplug_plug.html