In which three situations must you use a recovery catalog?

The correct answer is A. when you want to store RMAN global scripts that can be used across multiple databases D. when you want to list data files that were in a target database at a given time by using the AT E. when you want to maintain backup metadata longer than the period specified by the parameter. A: Some RMAN features function only when you use a recovery catalog. For example, you can store RMAN scripts in a recovery catalog. The chief advantage of a stored script is that it is available to any RMAN client that can connect to the target database and recovery catalog…

Managing Objects with Data Dictionary Views

Question

In which three situations must you use a recovery catalog?

Options

Awhen you want to store RMAN global scripts that can be used across multiple databases
Bwhen you want to restrict the amount of space used by backups
Cwhen you want to perform incremental backups by using a block change tracking file
Dwhen you want to list data files that were in a target database at a given time by using the AT
Ewhen you want to maintain backup metadata longer than the period specified by the parameter

How the community answered

(34 responses)

A
76% (26)
B
18% (6)
C
6% (2)

Explanation

A: Some RMAN features function only when you use a recovery catalog. For example, you can store RMAN scripts in a recovery catalog. The chief advantage of a stored script is that it is available to any RMAN client that can connect to the target database and recovery catalog. Command files are only available if the RMAN client has access to the file system on which they A local stored script is associated with the target database to which RMAN is connected when the script is created, and can only be executed when you are connected to this target database. A global stored script can be run against any database registered in the recovery catalog. D: If you use a recovery catalog, then you can use the atClause to specify a past time, SCN, or log sequence number, as shown in these examples of the command: RMAN> REPORT SCHEMA AT TIME 'SYSDATE-14'; # schema 14 days ago RMAN> REPORT SCHEMA AT SCN 1000; # schema at scn 1000 RMAN> REPORT SCHEMA AT SEQUENCE 100 THREAD 1; # schema at sequence 100 RMAN> REPORT SCHEMA FOR DB_UNIQUE_NAME standby1; E: The CONTROL_FILE_RECORD_KEEP_TIME initialization parameter determines the minimum number of days that records are retained in the control file before they are candidates for being overwritten. Thus, you must ensure that you resynchronize the recovery catalog with the control file records before these records are erased. https://docs.oracle.com/database/121/BRADV/rcmreprt.htm#BRADV90911

Topics

#recovery catalog#RMAN global scripts#backup metadata retention#block change tracking

Community Discussion

No community discussion yet for this question.

Full 1Z0-063 Practice