RMAN is connected to the target database prod1 and an auxiliary instance in nomount state. Examine the command to create a duplicate database: RMAN> DUPLICATE TARGET DATABASE TO dup1 FROM ACTIVE…

Question

Options

• AAll archive redo log files are automatically copied to the duplicate database.
• BThe duplicate database has the same directory structure as the source database.
• CThe duplicate database is created by using the backups created during the execution of
• Dhe duplicate command.
• EThe password file and SPFILE for the duplicate database dup1 are created in their respective
• FThe duplicate database is created without using RMAN backups and prod1 is allowed to

• A
  23% (7)
• B
  58% (18)
• C
  3% (1)
• D
  3% (1)
• E
  13% (4)

Explanation

FROM ACTIVE DATABASE is the critical keyword making F correct - it instructs RMAN to duplicate directly from the live target database over the network, requiring no pre-existing backups and leaving prod1 online throughout. NOFILENAMECHECK makes B correct - it tells RMAN to skip filename conflict validation, meaning the duplicate inherits the exact same directory structure and file paths as the source (only safe when the auxiliary is on a different host).

Why the distractors fail:

• A is wrong because only the archive logs needed for consistency are transferred, not all archive logs.
• C/D is wrong because FROM ACTIVE DATABASE streams datafiles live from the target - no backup set is created or used during duplication.
• E is a partial/misleading distractor; while PASSWORD FILE and SPFILE keywords do cause those files to be generated for the duplicate, that statement is not one of the two correct answers here.

Memory tip: Think of the two keywords as a pair - FROM ACTIVE DATABASE = "no backup, live clone" (F), and NOFILENAMECHECK = "same paths, no conflict check" (B). If you see both in a DUPLICATE command, options about backups being unnecessary and matching directory structure should both light up.

No community discussion yet for this question.