Examine the RMAN commands: RMAN> CONNECT TARGET "sbu@prod AS SYSBACKUP"; RMAN> CONNECT AUXILIARY "sbu@dup_db AS SYSBACKUP"; RMAN> DUPLICATE TARGET DATABASE TO dup_db FROM ACTIVE DATABASE PASSWORD…

Question

Options

• AIt succeeds and creates multisection backup sets that are used for active database duplication.
• BIt fails because there is no connection to a recovery catalog.
• CIt succeeds only if the target database is in MOUNT state.
• DIt fails because no parallel channels are allocated for the auxiliary database.

• A
  60% (18)
• B
  10% (3)
• C
  23% (7)
• D
  7% (2)

Explanation

Option A is correct because the SECTION SIZE 400M clause is valid syntax for active database duplication - it instructs RMAN to split datafiles into 400MB sections, creating multisection backup sets that enable parallel transfer to the auxiliary instance. This is a supported optimization for FROM ACTIVE DATABASE duplication and the command will execute successfully.

Why the distractors are wrong:

• B is wrong because a recovery catalog is entirely optional in RMAN; the target database's control file serves as the repository by default, so no CONNECT CATALOG is needed.
• C is wrong because FROM ACTIVE DATABASE duplication requires the target to be OPEN, not MOUNT - an open database is what makes the "active" copy possible.
• D is wrong because RMAN automatically allocates server-side channels during active duplication; you do not need to manually pre-allocate auxiliary channels for the command to succeed.

Memory tip: Think of SECTION SIZE as the "slice-and-dice" keyword - whenever you see it in a DUPLICATE or BACKUP command, it signals multisection backup sets are in play. If RMAN can slice it, it will succeed with it.

No community discussion yet for this question.