Recover Catalog: A base recovery catalog is a database schema that contains RMAN metadata for a set of target databases.

Benefits and Restrictions of RMAN in DataGuard

In easy words, RMAN metadata is stored in a different database instead of the control file. That database works as a repository.

Recovery catalog and data guard :

  • Use of the RMAN recovery catalog permits backups taken on one database server to be restored to another database server.
  • RMAN uses the recovery catalog transparently for all physical standby database associated with a primary database.
  • We should use the different database server to use for recovery catalog so we can use it efficiently in case of any disaster at any site in the Data Guard configuration does not affect the ability to recover from the latest

Now let us see a creation of recovery catalog.

We can create the recovery catalog in three easy steps.

  1. Configure the recovery catalog database.
  2. Create recovery catalog owner user
  3. Create recovery catalog

Configure recovery catalog database : 

We can create a database using dbca or we can use an existing database.

I am using demo database for recovery catalog.

Create recovery catalog owner user :

Here I am creating the specific tablespace for recover catalog owner and granting unlimited quota to that user.

  1. Creating tablespace

2. Creating user

3. Oracle have special grant ‘recovery_catalog_owner’ for recovery catalog owner.

Create recovery catalog :

4. connect with RMAN with catalog keyword

5. create the catalog using create catalog command.

Register database :

6. Register the primary database with the recovery catalog.

7. Register database using register database command.

Check details of the primary database using report schema command.

Setting RMAN Persistent Configuration setting 

We can use for db_unique_name clause to set a persistent setting in data guard environment.

Even we don’t need to connect to a primary database or physical standby database as a target.

We can use set dbid clause in RMAN session so that you can configure standby database when RMAN is not connected to a target to a database in data guard environment.

RMAN must be connected to the recovery catalog when we create or alter any configuration data guard environment.

For example

Setting RMAN Persistent Configuration setting for Primary Database

We can use the recovery catalog to set persistent configuration setting for the primary database.

  1. We can specify deletion policy for archive log.

2. Configure connect identifier for primary database and standby database

In next post, we will see offloading backup to Physical Standby Database with help of Recovery Catalog.

Offloading Backup to Standby in Data Guard

Stay tuned for More articles on Oracle DataGuard

Thank you for giving your valuable time to read the above information.

If you want to be updated with all our articles send us the Invitation or Follow us:

Telegram Channel :

Skant Gupta’s LinkedIn:

Joel Perez’s LinkedIn: Joel Perez’s Profile

LinkedIn Group: Oracle Cloud DBAAS

Facebook Page: OracleHelp

About The Author

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.