My Oracle Support Banner

Demystifying the RMAN Recovery Catalog (Doc ID 1362501.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.

Purpose

What is the function of the recovery catalog? What are the advantages and disadvantages of having a recovery catalog? Why do you need an RMAN recovery catalog when backups are first written to the controlfile, then resync'd to the catalog anyway?

Through out this note, the following databases will be used as examples:

RCAT - 11.2.0.3 database
ORA112 - 11.2.0.3 database
ORA102 - 10.2.0.5 database

 

Questions and Answers

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Questions and Answers
 1. What is the RMAN Catalog Schema, Repository and Database?
 2. Why Do You Need a Recovery Catalog?
 2.1 Long Retention Period
 2.2 Report schema as at a certain date
 2.3 RMAN Stored Scripts
 2.4 Dataguard Configuration
 3. What are the Disk Space and Memory Requirements?
 3.1 Backup Considerations
 3.2 Performance Considerations
 4. Implicit vs Explicit Resync
 5. How Do You Create The Recovery Catalog?
 6. Does a Target Upgrade also Mean a Catalog Upgrade?
 6.1 Which RMAN Executable to Use
 7. How do you Upgrade the RMAN Catalog?
 8. When Not to Use a Recovery Catalog
 8. 1 Test Restore
 8.2 Network Issues
 8.3 Catalog Issues
 9. Can You Query the RMAN Backend Views?
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.