Oracle Database Administration from Zero to Hero - Using RMAN Recovery Catalog (Part 2 of 3)

The video tutorial explains the process of resynchronization in RMAN, which updates the recovery catalogue with changes from the control files. It covers the two types of resynchronization: partial and full, and when to perform them manually. The tutorial also discusses cataloging recovery files to the RMAN repository, detailing the use of the catalog command to add backup pieces and data file copies. The video provides practical examples and scenarios where these processes are necessary.

What is the main purpose of resynchronization in RMAN?

• To synchronize the recovery catalog with changes in the control file

• To update the control file with new database users

• To delete old backup files

• To create new database instances

Which type of resynchronization includes changes to the database structure?

• Partial resynchronization

• Full resynchronization

• Differential resynchronization

• Incremental resynchronization

When is manual resynchronization required?

• When no changes are made to the database

• When the recovery catalog was unavailable during RMAN commands

• After every backup operation

• When the recovery catalog is always available

What is the process of adding recovery files to the RMAN repository called?

• Cataloging

• Synchronization

• Archiving

• Replication

Which command is used to add backup pieces to the RMAN repository?

• ADD BACKUP

• REGISTER BACKUP

• CATALOG BACKUP PIECE

• INSERT BACKUP

What must be true for a data file copy to be added to the RMAN repository?

• It must belong to a different database

• It must be older than a month

• It must be in a compressed format

• It must belong to the same database

What is a limitation of the catalog start with command?

• It can only be used once per session

• It cannot be used with wild card characters

• It only works with archived log files

• It requires manual intervention for each file