Avoiding RMAN-20208 when using a Flash Recovery Area and Recovering to a Previous Incarnation
(Doc ID 843636.1)
Last updated on OCTOBER 27, 2016
Applies to:Oracle Server - Enterprise Edition - Version: 10.2.0.4
Information in this document applies to any platform.
When a controlfile is restored and a flash recovery area is in use, RMAN will automatically
crosscheck backups and image copies in the restored controlfile against the flash recovery area
and catalog any objects in the FRA that are NOT in the restored controfile.
The objective is to simplify the recovery process and allow 'seamless' recovery through resetlogs
However, the recataloging of the archivelogs 're-introduces' the current incarnation in the
controlfile if the controlfile that is restored is from an earlier incarnation and this prevents
the database from opening after recovery if the database is only to be recovered to a point in
time in the previous incarnaton:
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.|