Registering a Database with a Recovery Catalog
Registering a database with a recovery catalog records the existence of the database with the recovery catalog. Once the database is registered metadata about the database and its backups will be stored in the recovery catalog.
This document will detail the process of registering a target database with a RMAN recovery catalog. This document assumes a base recovery catalog is in place and that all of the network settings have been made to allow connectivity to the recovery catalog. The examples were performed on Oracle 11gR2 running on Oracle Enterprise Linux.
Note: If you are using a Data Guard environment only the primary database can be registered in the method described in this document.
Registering a database with a recovery catalog is done with the
REGISTER DATABASE command.
Using RMAN, connect to both the target database (the database to register) and the recovery catalog.
[oracle@ora2 ~]$ rman target / catalog rcat@reccat Recovery Manager: Release 18.104.22.168.0 - Production on Wed Sep 1 13:42:51 2010 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. connected to target database: TESTDB (DBID=2502578563) recovery catalog database Password: connected to recovery catalog database RMAN>
Next issue the
REGISTER DATABASE command to register the database.
RMAN> register database; database registered in recovery catalog starting full resync of recovery catalog full resync complete RMAN>
When a database is registered with a recovery catalog for the first time a full catalog synchronization is performed (
RESYNC CATALOG). This process updates the catalog with the following information from the target database: database structure, backup records, archived redo log records and log history records detailing online log switches.
If you would like further verification that the registration completed successfully you can issue the command
LIST DB_UNIQUE_NAME ALL.
RMAN> list db_unique_name all; List of Databases DB Key DB Name DB ID Database Role Db_unique_name ------- ------- ----------------- --------------- ------------------ 2 TESTDB 2502578563 PRIMARY TESTDB RMAN>