A container database, CDB1, contains a pluggable database PDB1. Another container database is called CDB2. You want to relocate PDB1 from CDB1 to CDB2 with near-zero down time. Which three are…

Question

Options

• ACDB2 must be in shared UNDO mode only.
• BCDB2 must be in archivelog mode.
• CCDB1 must be in archivelog mode.
• DCDB1 and CDB2 must both be in local UNDO mode.
• ECDB1 must be in shared UNDO mode only.A container database, CDB1, contains a pluggable
• FCDB1 and CDB2 must be in shared UNDO mode.

• A
  12% (6)
• B
  80% (41)
• E
  6% (3)
• F
  2% (1)

Explanation

Near-zero downtime PDB relocation works by continuously shipping redo/archive logs from the source CDB to the destination CDB, keeping the copy in sync until a brief final cutover - this mechanism is why both CDB1 (C) and CDB2 (B) must be in archivelog mode. Local UNDO mode (D) is mandatory for both CDBs because it makes each PDB's undo data self-contained within the PDB itself, which is what allows the PDB to be physically moved; shared UNDO stores undo in the root container, making the PDB's data inseparable from the source CDB. Options A, E, and F are wrong for the same fundamental reason: shared UNDO mode is incompatible with PDB relocation regardless of which CDB has it - it breaks the portability requirement. Option F is doubly wrong because it requires both CDBs to use shared UNDO.

Memory tip: Think "A-L-L in" - both CDBs need Archivelog, and both need Local UNDO. If either CDB is in shared UNDO, the PDB is "chained" to its root and can't move.

No community discussion yet for this question.