Target Database Incarnation Is Not Current In Recovery Catalog RMAN-20011
(Doc ID 412113.1)
Last updated on AUGUST 08, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 10.1.0.2 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
*** ***
Symptoms
RMAN operations at the production site is failing during the resync phase when connected to the recovery catalog:
Changes
The target production database has recently been cloned to a development database. The clone operation was performed by an RMAN restore, a user-managed restore or snapshot copy.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |