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
RESETLOGSoperation on a database and later register it in the recovery catalog, the catalog records the
DB_NAMEfor the old incarnations as
UNKNOWNbecause the old incarnations were not previously registered. You should not try to remove these records.
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.
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
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:Oracle Database Utilities, to learn how to use the DBNEWID utility
% rman TARGET / CATALOG rman/rman@catdb RMAN> STARTUP FORCE MOUNT; RMAN> REGISTER DATABASE; RMAN> CATALOG DATAFILECOPY '?/oradata/system01.cpy'; RMAN> ALTER DATABASE OPEN;