Examine these 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 A. It succeeds. E. No catalogued backup of the TARGET is used to duplicate the database. A is correct because Oracle 12c introduced the SYSBACKUP privilege specifically for RMAN operations, making both the TARGET and AUXILIARY connections valid. The SECTION SIZE 400M clause enables multisection image copies (splitting large datafiles into parallel-copyable chunks)…

Backup and Recovery

Question

Examine these 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 FILE SECTION SIZE 400M; Which two statements are true about the DUPLICATE command?

Options

AIt succeeds.
BIt fails because no parallel channels are allocated for the auxiliary database.
CIt fails because connection to the AUXILIARY instance must be as SYSDBA.
DItsucceeds only if the target database is greater than 400M.
ENo catalogued backup of the TARGET is used to duplicate the database.

How the community answered

(37 responses)

A
81% (30)
B
3% (1)
C
11% (4)
D
5% (2)

Explanation

A is correct because Oracle 12c introduced the SYSBACKUP privilege specifically for RMAN operations, making both the TARGET and AUXILIARY connections valid. The SECTION SIZE 400M clause enables multisection image copies (splitting large datafiles into parallel-copyable chunks) and is syntactically legal regardless of database size. E is correct because FROM ACTIVE DATABASE duplicates by streaming datafiles directly from the live target instance over Oracle Net - no catalog, no backup sets, no archived backups are involved at all.

B is wrong because FROM ACTIVE DATABASE causes RMAN to automatically allocate default server-side channels for both target and auxiliary; manual channel allocation is not required. C is wrong because SYSBACKUP (introduced in 12c) is a fully supported privilege for RMAN auxiliary connections - SYSDBA is not required. D is wrong because SECTION SIZE defines the maximum chunk size for multisection copies of individual datafiles; it does not impose a minimum database size requirement - a database smaller than 400M simply produces single-section files.

Memory tip: Think of FROM ACTIVE DATABASE as a live "network clone" - it goes straight from the source instance to the destination, skipping the catalog entirely (hence E). And remember "SYSBACKUP = RMAN's own privilege" - Oracle 12c gave RMAN its own dedicated administrative role so SYSDBA is no longer needed.

Topics

#RMAN DUPLICATE#Active Database Duplication#SYSBACKUP Authentication#Backup Restoration

Community Discussion

No community discussion yet for this question.

Full 1Z0-083 Practice