Applies to:Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.3 - Release: 10.2 to 10.2
Information in this document applies to any platform.
***Checked for relevance on 22-Mar-2011***
Physical Standby Database Setup.
The Standby database has been activated (open read/write, resetlogs done), then using Flashback to recover it back to Physical Standby Status. During flashback, it could not recover due to a corrupted archive log.
After Restore backup past that corrupted Point, MRP will get this Error:
ORA-00283: recovery session canceled due to errors
ORA-19909: datafile 1 belongs to an orphan incarnation
ORA-01110: data file 1: '/oracle/oradata/PROD/oradg07/PROD_system01_4096m'
The Standby Database has been activated, then flashback to be Physical Standby again.
This is caused by Bug 6035495 ORA-19909 during MRP / RMAN-600 on resync
Fixed-Releases: 10.2.0.4, 188.8.131.52
ORA-19909 during MRP or RMAN-600 (8201) during RMAN resync can occur.
MRP encounter same error and standby has resetlogs done
The Problem here is the Primary Database has only 1 incarnation:
While the Standby Database has 2 Incarnations due to Activation:
The CURRENT Incarnation on Standby Database is 2 which is different from Primary Database Incarnation 1. That is why ORA-19909 reported when recovery is done.
The incarnation is recorded in Datafile Header, so simply recreating the Standby Controlfile will not help.
The Solution is to find out the CURRENT Incarnation from the Primary Database, reset the Standby Database Incarnation to match the Primary Database using rman command:
reset database to incarnation <key>
then perform Recovery.
In this sample:
Primary Database Incarnation is 1
Standby Database Incarnation is 2
On the Standby Site:
Check alert log, it should continue Managed Recovery now.
To avoid such situation in future please apply at least 10.2.0.4 Server Patch Set which includes
the fix for this.