RMAN Commands , 40 of 59

REGISTER

Syntax

Text description of the illustration register.gif

Purpose

To register the target database in the recovery catalog so that RMAN can access it. RMAN obtains all information it needs to register the target database from the target database itself.

Note:

If you perform a RESETLOGS operation on a database and later register it in the recovery catalog, the catalog records the DB_NAME for the old incarnations as UNKNOWN because the old incarnations were not previously registered. You should not try to remove these records.

Restrictions and Usage Notes

Execute this command only at the RMAN prompt.
You must be connected to the target database and recovery catalog database.
You can register multiple databases in the same recovery catalog, but the database identifiers of the databases must be unique.
You can only register a database once in a given recovery catalog.
The target database must be mounted or open.
You should not register a standby database.

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 standalone DBNEWID utility.

Note:

If you are using RMAN with different target databases that have the same database name and DBID, be careful to always specify the correct recovery catalog schema when invoking RMAN.

See Also:

Oracle9i Database Utilities, to learn how to use the DBNEWID utility

Example

Registering a Database: Example

The following shell script registers a new target database, catalogs an existing datafile copy, then opens the database for use:

rman TARGET / CATALOG rman/rman@catdb <<EOF
STARTUP FORCE MOUNT;
REGISTER DATABASE;
CATALOG DATAFILECOPY '?/oradata/system01.cpy';
ALTER DATABASE OPEN;
EXIT;
EOF