My Oracle Support Banner

RMAN restore database fails with RMAN-20011, Target Incarnation Is Not Current (Doc ID 394493.1)

Last updated on JANUARY 17, 2023

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 8.1.7 to 10.2]
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.


You are attempting to restore the database with RMAN. You know the restore time is in a previous incarnation. You have already reset the incarnation:
The database is mounted. RMAN> restore database; fails with RMAN-20011.

Error: RMAN 20011
Text: 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 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.


Resetted the incarnation of the database marked as CURRENT, to a prior RESETLOGS SCN.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.