Which three are true about cloning databases into an existing CDB with RMAN?

Question

Options

• AA non-CDB can be cloned into a PDB.
• BA user with SYSDBA or SYSBKUP must be logged in with RMAN to CDB$ROOT when
• COnly one PDB can be cloned at a time.
• DTwo or more PDBs can be cloned with the same command.
• EA user with SYSDBA or SYSBKUP must be logged in with RMAN to the non-CDB being
• FThe target and auxiliary instance passwords must be the same.

• A
  18% (4)
• B
  68% (15)
• D
  9% (2)
• F
  5% (1)

Explanation

When cloning into an existing CDB with RMAN, B is correct because RMAN requires a connection to CDB$ROOT (not an individual PDB) with SYSDBA or SYSBACKUP privilege - this is the auxiliary instance connection that gives RMAN authority over the entire container. E is correct because RMAN also needs that same level of privilege connected to the source (the non-CDB or source database being cloned), forming the target connection. C is correct because RMAN's DUPLICATE command for cloning into an existing CDB processes one PDB per command - D is therefore wrong.

A is wrong because a non-CDB cannot be directly cloned into a PDB via RMAN in a single step; non-CDB-to-PDB migration requires the DBMS_PDB package approach (generate an XML manifest, then plug in), not a direct RMAN clone. F is wrong because the target and auxiliary instance passwords are independent - RMAN connects to each with its own credentials and they do not need to match.

Memory tip: Think of the two required privilege connections as a handshake - one hand on the root of the destination CDB (B), one hand on the source being cloned (E), and you can only shake one hand at a time (C).

No community discussion yet for this question.