Demystifying the RMAN Recovery Catalog (Doc ID 1362501.1)

Last updated on MAY 13, 2020

Applies to:

Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.

Purpose

******************************************************************************

NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner. For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:

Oracle SID - Database Release
------------------------------------
RCAT - 11.2.0.3 database
ORA112 - 11.2.0.3 database
ORA102 - 10.2.0.5 database

******************************************************************************

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?