ORA-19906: recovery target incarnation changed during recovery
Answer / guest
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.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
RMAN-08027: channel string: copied current controlfile
LPX-00257: invalid children specification in element declaration
ORA-12646: Invalid value specified for boolean parameter
RMAN-06181: multiple channels require Enterprise Edition
TNS-01190: The user is not authorized to execute the requested listener command
ORA-25125: BUFFER_POOL storage option not allowed
NZE-28773: failure to write magic and version numbers
ORA-07272: spwat: invalid semaphore set id.
ORA-08237: smsget: SGA region not yet created
ORA-16558: The database specified for switchover is not a standby.
ORA-01252: cannot prevent writes - file string in recovery manager backup
ORA-13044: the specified tile size is smaller than the tolerance