ORA-19906 Frequently on Physical Standby

(Doc ID 960653.1)

Last updated on DECEMBER 06, 2017

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 10.1 to 11.2]
Oracle Database - Enterprise Edition - Version to [Release 12.1]
Information in this document applies to any platform.
***Checked for relevance on 27-Sep-2012***
***Checked for relevance on 06-Aug-2014***


Physical standby setup. Physical standby was activated accidentally on Fri Aug 07 09:20:50, incarnation was  increased to 15 at that time, while primary was still running with incarnation 14. Then standby was rebuilt using fresh backup from primary and continued with recovery.

But every time delete Oracle managed file from db_recovery_area happens, it always follows by incarnation change, for example:

Fri Aug 07 17:00:17 2009
Deleted Oracle managed file /opt/oracle/share/flash_recovery_area/DB_2/flashback/o1_mf_526gg3co_.flb
Deleted Oracle managed file /opt/oracle/share/flash_recovery_area/DB_2/flashback/o1_mf_526kkg8b_.flb
Setting recovery target incarnation to 15

This caused standby to report ORA-19906:

ORA-19906: recovery target incarnation changed during recovery
Fast Parallel Media Recovery enabled
Managed Standby Recovery starting 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 60565076) is orphaned on incarnation#=14
MRP0: Background Media Recovery terminated with error 19909
Errors in file
ORA-19909: datafile 1 belongs to an orphan incarnation
ORA-01110: data file 1: '/opt/oracle/db_2/database/system01.dbf'
Managed Standby Recovery not using Real Time Apply

Despite how many times standby rebuilt, it always report such error soon after rebuilt.


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