Effect of doing PITR (point in time recovery) / Flashback on PRIMARY when Physical Standby in place ORA-19906 ORA-19909 ORA-01110

(Doc ID 824213.1)

Last updated on AUGUST 29, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.

Symptoms

Media recovery process (MRP) in Physical standby database terminates with the below errors after PITR or Flashback done on PRIMARY database

RFS[4]: Incarnation entry added for Branch(resetlogs_id): 686768021 (prim)
Wed May 13 16:54:17 2009
Setting recovery target incarnation to 2
Wed May 13 16:54:22 2009
MRP0: Incarnation has changed! Retry recovery...
Wed May 13 16:54:22 2009
Errors in file /u01/prim/bdump/prim_mrp0_1814.trc:
ORA-19906: recovery target incarnation changed during recovery
Recovery interrupted!
Wed May 13 16:54:23 2009
Errors in file /u01/prim/bdump/prim_mrp0_1814.trc:
ORA-19906: recovery target incarnation changed during recovery
Wed May 13 16:54:43 2009
Managed Standby Recovery not using Real Time Apply
Warning: Recovery target destination is in a sibling branch
of the controlfile checkpoint. Recovery will only recover
changes to datafiles.
Datafile 1 (ckpscn 908075) is orphaned on incarnation#=1
MRP0: Background Media Recovery terminated with error 19909
Wed May 13 16:54:43 2009
Errors in file /u01/prim/bdump/prim_mrp0_1814.trc:
ORA-19909: datafile 1 belongs to an orphan incarnation
ORA-01110: data file 1: '/u01/prim/data/system01.dbf'

Cause

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 hundreds of Community platforms