Which three capabilities require the use of the RMAN recovery catalog? (Choose three.)
Which three capabilities require the use of the RMAN recovery catalog? (Choose three.)
The capabilities that require the use of the RMAN recovery catalog are: using the KEEP FOREVER clause with the BACKUP command, using RMAN stored scripts, and using the REPORT SCHEMA command to list a database's data files and tablespaces at times in the past. Firstly, the KEEP FOREVER clause necessitates a recovery catalog because the backup records will eventually age out of the control file. Secondly, RMAN stored scripts require a recovery catalog as these scripts are stored in the catalog. Lastly, the REPORT SCHEMA command to list data files and tablespaces at past times also requires a recovery catalog since it needs historical metadata stored in the catalog.
A, B, F
ABF are definitely correct: A is correct: https://docs.oracle.com/en/database/oracle/oracle-database/19/rcmrf/keepOption.html "Specifies that the backup or copy never becomes obsolete (see Example 2-27). A recovery catalog is required when FOREVER is specified because the backup records eventually age out of the control file." B is correct: https://docs.oracle.com/database/121/RCMRF/rcmsynta013.htm "Execute CREATE SCRIPT only at the RMAN prompt. RMAN must be connected to a target database and a recovery catalog." F is correct: https://docs.oracle.com/en/database/oracle/oracle-database/19/rcmrf/REPORT.html "atClause This subclause specifies a point in time as a time, SCN, or log sequence number. You must be connected to a recovery catalog when issuing a REPORT SCHEMA command with an AT clause."
B is correct, however, the answer is about running scripts, not executing them. The correct documentation is this: https://docs.oracle.com/en/database/oracle/oracle-database/23/rcmrf/EXECUTE-SCRIPT.html#GUID-553B5C55-0BA6-4B47-86A9-0BCF839CCE04
A Recovery Catalog is required with Keep Forever B Scripts are stored in the Catalog F Report Schema of all datafiles and tablespace, required recovery catalog
Agree with ABF
F is wrong: "For REPORT SCHEMA without forDbUniqueNameOption, a target database connection is required, but a recovery catalog connection is optional. ". This question specifies "Which three capabilities require ". Required, not optional. REF: https://docs.oracle.com/en/database/oracle/oracle-database/19/rcmrf/REPORT.html#GUID-8352987F-533A-4146-A157-F091103169B0 D is correct: the only way we have a customized report about a database backups is through stored scripts, which require catalog. ABD are the correct answers
agreed with this.
Agreed
sorry, F is true, 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: https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/reporting-rman-operations.html#GUID-D14C8A12-E9A6-484D-A8AD-7E40BA714740
A, B and F are the correct options.
I think A, B, F are correct. I tested F. Without connection to recovery catalog I executed - RMAN> report schema at scn 2422100; (at SCN in the past in my database 19.3) and I've got the error: RMAN-06137: must have recovery catalog for REPORT SCHEMA AT TIM
I agree with ABF
A, B, F
ABF D wrong. you can do reports in this way: When the database is open, several V$ views provide direct access to RMAN repository records in the control file of each target database. Some V$ views such as V$DATAFILE_HEADER, V$PROCESS, and V$SESSION contain information not found in the recovery catalog views. https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/reporting-rman-operations.html#GUID-1C655AF1-B3CD-452C-BC3C-A566912311FF F is true, 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: https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/reporting-rman-operations.html#GUID-D14C8A12-E9A6-484D-A8AD-7E40BA714740
A. True B. False: global scripts are stored in RC, but local scripts are stored in controlfile C. False: report schema works when connected to target DB D. Not sure of what it means. Maybe single database means "any DB cataloged in RC"? E. False: works without RC F. True: RC full sync takes snapshot of controlfile, so I think it should be possible
nvm. I'm going with ABF