You want to drop a pluggable database from a multitenant container database that is used for development, which two statements are true?

Question

Options

• AYou can drop the PDB only if it is closed.
• BYou can drop the seed PDB, but you cannot create any other PDB within the CDB.
• CYou can drop the PDB and keep the data files to be reused by another PDB.
• DWhen you drop the PDB, the data files and redo log files are automatically removed from the

• A
  83% (54)
• B
  5% (3)
• D
  12% (8)

Explanation

DROP PLUGGABLE DATABASE Use the DROP PLUGGABLE DATABASE statement to drop a pluggable database (PDB). When you drop a PDB, the control file of the multitenant container database (CDB) is modified to remove all references to the dropped PDB and its data files. Archived logs and backups associated with the dropped PDB are not deleted, but you can use Oracle Recovery Manager (RMAN) to delete them. You must be connected to a CDB. The current container must be the root, you must be authenticated AS SYSDBA or AS SYSOPER, and the SYSDBA or SYSOPER privilege must be either granted to you commonly, or granted to you locally in the root and locally in PDB you want to drop. The PDB you want to drop must be in mounted mode or it must be unplugged. Specify KEEP DATAFILES to retain the data files associated with the PDB after the PDB is dropped. The temp file for the PDB is deleted because it is no longer needed. This is the default. Keeping data files may be useful in scenarios where a PDB that is unplugged from one CDB is plugged into another CDB, with both CDBs sharing storage devices. INCLUDING DATAFILES Specify INCLUDING DATAFILES to delete the data files associated with the PDB being dropped. The temp file for the PDB is also deleted.

No community discussion yet for this question.