RMAN-20011: target database incarnation is not current in recovery catalog

Cause: The database incarnation that matches the resetlogs change# and time of the mounted target database control file is not the current incarnation of the database.

Action: If RESET DATABASE TO INCARNATION key was used to make an old incarnation current, then restore the target database from a backup that matches the incarnation and mount it. You will need to do STARTUP NOMOUNT before you can restore the control file using RMAN. Otherwise use RESET DATABASE TO INCARNATION key to make the intended incarnation current in the recovery catalog.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

RMAN-20010: database incarnation not found

Cause: Database incarnation does not match any database incarnation in the recovery catalog.

Action: Specify a valid database incarnation key.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

RMAN-20009: database incarnation already registered

Cause: This incarnation is already registered in the recovery catalog. This is an informational message.

Action: No action required.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

RMAN-20008: database incarnation key is missing

Cause: The database incarnation key was not specified.

Action: Specify a valid database incarnation key.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

RMAN-20007: target database id is missing

Cause: This an internal error.

Action: Contact Oracle Support Services.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

RMAN-20006: target database name is missing

Cause: The target database instance is not started or the value of the DB_NAME initialization parameter is not set.

Action: Start the instance and make sure that the value of the DB_NAME initialization parameter is set.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

RMAN-20005: target database name is ambiguous

Cause: Two or more databases in the recovery catalog match the DB_NAME initialization parameter of the instance and the target database is not mounted, so RMAN cannot get its DBID.

Action: Mount the target database then retry the operation.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

RMAN-20004: target database name does not match name in recovery catalog

Cause: Name of the target database does not match the one stored in the recovery catalog. This is an internal error.

Action: Contact Oracle Support Services.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

RMAN-20003: target database incarnation not found in recovery catalog

Cause: Resetlogs change# and/or time of the target database does not match any database incarnation in the recovery catalog.

Action: If target database was opened with resetlogs option then use RESET DATABASE to register the new incarnation.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

RMAN-20002: target database already registered in recovery catalog

Cause: Target database is already registered in the recovery catalog.

Action: If the target database is really registered, there is no need to register it again. Note that the recovery catalog enforces that all databases have a unique DBID. If the new database was created by copying files from an existing database, it will have the same DBID as the original database and cannot be registered in the same recovery catalog.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/