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

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

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

A.
to store backup information of multiple databases in one place

B.
to restrict the amount of space that is used by backups

C.
to maintain a backup for an indefinite period of time by using the KEEP FOREVER clause

D.
to store RMAN scripts that are available to any RMAN client that can connect to target
databasesregistered in the recovery catalog

E.
to automatically delete obsolete backups after a specified period of time

Show Hint

Leave a Reply 12

Your email address will not be published. Required fields are marked *

MJ

MJ

C and D for sure, but not so sure about E. A appears to be true. It might be ACD

Reply

sail_96

sail_96

The answer is ACD.

E is not true because you could do that with the retention policy even if you are not connected to a recovery catalog.

keepOption – Overrides any configured retention policy for this backup so that the backup is not considered obsolete, as shown in Example 2-25.
You can use the KEEP syntax to generate archival database backups that satisfy business or legal requirements. The KEEP setting is an attribute of the backup set (not individual backup piece) or image copy.

Note: You cannot use KEEP with BACKUP BACKUPSET.

With the KEEP syntax, you can keep the backups so that they are considered obsolete after a specified time (KEEP UNTIL), or make them never obsolete (KEEP FOREVER). As shown in Example 2-26, you must be connected to a recovery catalog when you specify KEEP FOREVER.

Note: You can use CHANGE to alter the status of a backup generated with KEEP.

Note: You cannot use KEEP UNTIL with PLUS ARCHIVELOG.

Reply

max

max

ACD
C
FOREVER Specifies that the backup or copy never becomes obsolete (see Example 2-26). A recovery catalog is required when FOREVER is specified because the backup records eventually age out of the control file.

Reply

Big-G

Big-G

A C D

A:
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”

C:
https://docs.oracle.com/database/121/BRADV/rcmmaint.htm#BRADV8173
”
Note:
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.”

D:
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 file system.”

Reply