Examine this output of an export from the current release of an Oracle multitenant database: $ sqlplus system/oracle. SQL> col name for a10 SQL> select name, open_mode from v$pdbs; NAME OPEN_MODE…

Question

Options

• AIt fails because Data Pump cannot be container.
• BIt creates a full export of the root container and all PDBs.
• CIt creates a full export of the root container and all open PDBs.
• DIt creates a full export of only the used while connected to the root container and PDB1.

• A
  91% (20)
• B
  5% (1)
• D
  5% (1)

Explanation

Running expdp system/oracle full=y while connected to the CDB root fails in Oracle 12c multitenant because Data Pump does not support full database exports executed from within the root container (CDB$ROOT) - to export a PDB, you must connect Data Pump directly to that specific PDB, not to the root. Option B is wrong because even if the command ran, PDB-level data is not accessible via a root-level full=y export. Option C is wrong for the same reason - the open/mounted state of PDBs is irrelevant since the export fails before any PDB content is considered. Option D is wrong because there is no mechanism by which this command selectively combines root and PDB1; it would either export the root alone or fail entirely, and in the multitenant context it fails.

Memory tip: Think "connect where you want to export." In Oracle multitenant, Data Pump must be connected inside the container it's exporting - root exports root, PDB1 exports PDB1. Running full=y from the root is like trying to pack someone else's suitcase from the hotel lobby.

No community discussion yet for this question.