ORA-19912: cannot recover to target incarnation string

ORA-19912: cannot recover to target incarnation string

Cause: The control file is not in the recovery path of the target incarnation, and does not contain enough information as to how to recover to the target incarnation.

Action: Restore the latest control file from the target incarnation and retry.

ORA-19911: datafile string contains future changes at the incarnation boundary

ORA-19911: datafile string contains future changes at the incarnation boundary

Cause: The file did not hit end backup marker redo during recovery at the incarnation boundary, hence may contain changes discarded by new incarnation.

Action: Use older backup of the file and then re-issue the command.

ORA-19910: can not change recovery target incarnation in control file

ORA-19910: can not change recovery target incarnation in control file

Cause: The RESET DATABASE TO INCARNATION command was used while the database is open. This is not allowed.

Action: Close the database then re-issue the command.

ORA-19909: datafile string belongs to an orphan incarnation

ORA-19909: datafile string belongs to an orphan incarnation

Cause: Either the specified datafile was restored from a backup that was taken during a period of time that has already been discarded by a resetlogs operation, or Oracle cannot identify which database incarnation the file belongs to. The alert log contains more information.

Action: Restore a backup of this file that belongs to either the current or a prior incarnation of the database. If you are using RMAN to restore, RMAN will automatically select a correct backup.

ORA-19908: datafile string has invalid checkpoint

ORA-19908: datafile string has invalid checkpoint

Cause: The specified datafile has an invalid checkpoint.

Action: Restore the datafile from a backup.

ORA-19907: recovery time or SCN does not belong to recovered incarnation

ORA-19907: recovery time or SCN does not belong to recovered incarnation

Cause: A point-in-time recovery to an SCN or timestamp prior to the last resetlogs was requested.

Action: Either change the specified recovery time or scn, or change the recovery destination using RMAN s RESET DATABASE command.

ORA-19906: recovery target incarnation changed during recovery

ORA-19906: recovery target incarnation changed during recovery

Cause: While a media recovery was active, a new incarnation was detected by the server due to inspection or cataloging of archived logs or backup files.

Action: If you want recovery to use the new incarnation, restart recovery. This is the most common action on a standby database when resetlogs is done in primary. If you do not want recovery to use the new incarnation, change the recovery destination using RMAN s RESET DATABASE TO INCARNATION lamp;lt;lamp;nbsp;incarnation#lamp;gt; command. To see which incarnations are available for this target database, query V$DATABASE_INCARNATION or use RMAN s LIST INCARNATION command.