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 <incarnation#> command. To see which incarnations are available for this target database, query V$DATABASE_INCARNATION or use RMAN's LIST INCARNATION command.
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 <incarnation#> command. To see which incarnations are available for this target database, query V$DATABASE_INCARNATION or use RMAN's LIST INCARNATION command.
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 <incarnation#> command. To see which incarnations are available for this target database, query V$DATABASE_INCARNATION or use RMAN's LIST INCARNATION command.
