RMAN-20011: target database incarnation is not current in
recovery catalog
- 1 Answers
- 9739 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: the database incarnation that matches the resetlogs
change# and time of the mounted target database controlfile
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 controlfile using RMAN. Otherwise use 'reset
database to incarnation <key>' make the intended incarnation
current in the recovery catalog.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-22882: object creation failed
ORA-26099: direct path context is already prepared
ORA-15060: template "string" does not exist
DRG-13312: user CTXSYS does not own USER_LEXER stored procedure string
NID-00320: Operation cancelled at user request
ORA-16501: the Data Guard broker operation failed
DRG-10204: server update failed
PLS-00614: creating a FINAL NOT INSTANTIABLE type
ORA-13036: Operation [string] not supported for Point Data
SQL*Loader-00521: lfilini failed for file (string)
ORA-12823: default degree of parallelism may not be specified here
ORA-08320: scnget: Call to scnget before scnset or scnfnd.
Oracle Errors 
