Identify three reasons for using a recovery catalog with Recovery Manager (RMAN).

Question

Options

• Ato store backup information of multiple databases in one place
• Bto restrict the amount of space that is used by backups
• Cto maintain a backup for an indefiniteperiod of time by using the KEEPFOREVERclause
• Dto store RMAN scripts that are available to any RMAN client that can connect to target
• Eto automatically delete obsolete backups after a specified period of time

• A
  77% (54)
• B
  9% (6)
• E
  14% (10)

Explanation

https://docs.oracle.com/database/121/BRADV/rcmarchi.htm#GUID-D5EBBDAF-5392-4D75- B919-A298F6C0881E "You can also create a recovery catalog, which is a repository of RMAN metadata stored in an Oracle Database schema. The control file has limited space for records of backup activities, whereas a recovery catalog can store a much longer history. You can simplify backup and recovery administration by creating a single recovery catalog that contains the RMAN metadata for all of your databases" https://docs.oracle.com/database/121/BRADV/rcmmaint.htm#BRADV8173 The KEEP FOREVER clause requires the use of a recovery catalog, because the control file cannot contain an infinitely large set of RMAN repository data." https://docs.oracle.com/database/121/BRADV/rcmcatdb.htm#BRADV89669 "You can use a stored script as an alternative to a command file for managing frequently used sequences of RMAN commands. The script is stored in the recovery catalog rather than on the

No community discussion yet for this question.