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' make the intended incarnation current in the recovery catalog.
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' make the intended incarnation current in the recovery catalog.
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' make the intended incarnation current in the recovery catalog.
