1Z0-063 · Question #234
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…
The correct answer is D. It succeeds and creates multisection backup sets that are used for active database duplication. See the full explanation below for the reasoning.
Question
Options
- AIt fails because there is no connection to a recovery catalogue.
- BIt fails because no parallel channels are allocated for the auxiliary database.
- CIt succeeds only if the target database is in MOUNT state.
- DIt succeeds and creates multisection backup sets that are used for active database duplication.
How the community answered
(54 responses)- A4% (2)
- B7% (4)
- C15% (8)
- D74% (40)
Community Discussion
6
Luis F.Jun 22, 2026The answer is D, and here is why it makes sense once you break it down. The SECTION SIZE 400M clause is the key, because that tells RMAN to split large datafiles into 400MB sections and transfer them as multisection backup sets directly over the network from the target to the auxiliary, which is exactly what active database duplication does. You do not need a recovery catalog for this to work, so A is out, and RMAN automatically allocates default channels when you do not specify any, so B is also wrong. C trips people up because active duplication actually requires the TARGET to be OPEN, not mounted, since RMAN is reading live datafiles straight from the source instance.
Toby R.Jun 9, 2026D is right. When you use SECTION SIZE with FROM ACTIVE DATABASE, RMAN breaks the datafiles into multisection pieces and transfers them directly to the auxiliary instance over the network without needing a catalog or pre-allocated channels.
Ola B.Jun 27, 2026D is right, though "multisection" is the detail that trips people, spin up a lab and watch it work.
Carlos M.Jun 29, 2026Lab confirms it fast, but if you are short on time, just remember that multisection forces LSA type 3 summarization at the ABR, which is exactly what the question is testing.
Samuel O.Jun 17, 2026D is right. When you use SECTION SIZE in an active database duplicate, RMAN breaks the datafiles into multisection backup sets on the fly and ships them directly to the auxiliary, so you never need a catalog connection or pre-allocated channels on that side.
Carlos M.Jun 21, 2026Thought C, but PASSWORD FILE and SECTION SIZE 400M confirms active dup with multisection sets, so D.