Which three are true about Recovery Manager (RMAN) active database duplication?

The correct answer is D. Image copies can be used to duplicate the active database. F. No connection to the recovery catalog is required for active database duplication. G. Backup sets can be used to duplicate the active database. Active database duplication in RMAN transfers data directly from the live source database to the auxiliary instance over the network - no pre-existing backups are required. D and G are correct because RMAN supports both image copies and backup sets as the transport format…

Backup and Recovery

Question

Options

APre-existing backups of the database to be duplicated are required for the "push" method of
BPre-existing backups of the database to be duplicated are required for the "pull" method of
CPre-existing backups of the database to be duplicated are always used if they exist.
DImage copies can be used to duplicate the active database.
EThe active database must be duplicated while in OPEN state.
FNo connection to the recovery catalog is required for active database duplication.
GBackup sets can be used to duplicate the active database.

How the community answered

(37 responses)

A
3% (1)
C
8% (3)
D
84% (31)
E
5% (2)

Explanation

Active database duplication in RMAN transfers data directly from the live source database to the auxiliary instance over the network - no pre-existing backups are required. D and G are correct because RMAN supports both image copies and backup sets as the transport format during active duplication (via push or pull methods). F is correct because active duplication connects directly to the target and auxiliary instances; the recovery catalog is entirely optional.

Why the distractors fail:

A & B are wrong because neither the push nor pull method requires pre-existing backups - that's the defining feature of active duplication; data comes straight from the live database.
C is wrong because RMAN does not automatically fall back to existing backups during active duplication; backups are simply ignored unless you explicitly configure backup-based duplication.
E is wrong because the source database can be in either MOUNT or OPEN state - OPEN is common but not mandatory.

Memory tip: The word active means "from the live database, right now." Active duplication = no backups needed (eliminates A, B, C), catalog is optional (F), and both data formats work - image copies (D) and backup sets (G). The only state myth to bust is E: MOUNT is also valid.

Topics

#Active Database Duplication#RMAN#Backup Methods#Recovery Catalog

Community Discussion

Marisol N.May 20, 2026

The correct answers are D, F, and G. Active database duplication does not require pre-existing backups at all (ruling out A, B, and C), it works from OPEN or MOUNT state (ruling out E), it supports both image copies and backup sets as the transport mechanism, and the recovery catalog is optional because RMAN gathers metadata directly from the target control file. Memory hook: active duplication means "live source, your choice of format, no catalog needed." This item maps to the Oracle 1Z0-083 objective "Back Up and Recover a Database, Using RMAN" and specifically the sub-topic on active database duplication methods.

Mei-Ling H.Apr 27, 2026

I almost picked C and E because I assumed backups would be used automatically if present and that the source must be fully open, but "always" in option C is the trap word here since active duplication specifically streams live datafiles over the network and ignores any existing backups entirely. Once I confirmed that the auxiliary instance only needs a connection to the target, not a catalog, and that both image copies and backup sets are valid transfer formats in active duplication, D, F, and G locked in cleanly.

Nina C.Apr 29, 2026

Good catch on the "always" trap, and worth adding that backup sets are only valid for active duplication starting in 12c with the USING BACKUPSET clause, so if your exam scope includes 11g behavior, image copies are the only transfer format active dup supports.

Nina C.May 6, 2026

I went with E at first because I kept thinking "active" meant the database had to be actively open, but then I remembered from the docs that the source just needs to be mounted or open, so that one falls apart. What locked in D, F, and G for me was realizing active duplication pushes or pulls datafiles directly over the network from the source, so you do not need pre-existing backups at all, a recovery catalog connection is optional, and Oracle supports both image copies and backup sets as the transfer format.

Samuel O.Apr 19, 2026

D, F, and G are solid picks. Active duplication transfers files directly over the network from the target to the auxiliary, so you never need pre-existing backups, you can use either backup sets or image copies for the transfer, and the catalog connection is optional because RMAN pulls what it needs straight from the target controlfile.

Lena V.Apr 28, 2026

Going with A, D, and G on this one. The push method in active duplication has the auxiliary instance connect to the target and catalog, but the target server process is what ships the data, and Oracle's documentation makes clear that pre-existing backups are needed on the push side because the target cannot stream directly without something staged first. D and G are straightforward, image copies and backup sets both work for active duplication, that comes up constantly in the practice material. I keep seeing people confuse push vs pull mechanics here, but the key distinction is which side initiates the data transfer and what resources each side needs ready before duplication starts. Lock in A, D, G and move on.

-2

Full 1Z0-083 Practice