Purpose

Use the REGISTER DATABASE command to register the target database in the recovery catalog so that RMAN can maintain its metadata. RMAN obtains all information it needs to register the target database from the target database itself.

Prerequisites

Execute this command only at the RMAN prompt. RMAN must be connected to a recovery catalog and a mounted or open target database. The database that you are registering must not be currently registered in the recovery catalog.

You can only register a target database with a DBID that is unique within the recovery catalog. Databases with the same name are permitted if the DBID values are different. The database that you are registering must not be a standby database.

Usage Notes

RMAN automatically registers a new standby database in the recovery catalog when the primary database for the standby database is registered in the recovery catalog and either of the following conditions is true:

• RMAN is connected to a database instance that has a DB_UNIQUE_NAME unknown to the recovery catalog.

• You execute the CONFIGURE DB_UNIQUE_NAME command for a database that is not known to the recovery catalog.

The REGISTER DATABASE command fails when RMAN detects duplicate DBIDs. This situation can arise when databases are created by copying files from an existing database rather than by using the DUPLICATE command. If this failure occurs, then you can change the DBID of the copied database with the DBNEWID utility and then retry the REGISTER DATABASE command.

If you open a database with the RESETLOGS option and later register this database in the recovery catalog, then the recovery catalog records the DB_NAME for the old incarnations as UNKNOWN because the old incarnations were not previously registered. Do not try to remove these records.

Syntax

register::=

Description of the illustration register.eps

Example