My Oracle Support Banner

After failover, reinstate of old primary fails with ORA-16795 even though flashback is enabled (Doc ID 2121460.1)

Last updated on AUGUST 04, 2018

Applies to:

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

Symptoms

After failover, reinstate of old primary  fails with ORA-16795 even though flashback is enabled :


DGMGRL> reinstate database dgdb    
ORA-16795: the standby database needs to be re-created

Configuration details cannot be determined by DGMGRL

 

Following messages were seen in the broker log :

 

Preparing database for reinstatement
03/17/2016 09:22:10
Notifying DMON of db close
Notifying RSM0 of db close
03/17/2016 09:22:12
Data Guard Broker shutting down
RSM0 successfully terminated
2016-03-17 09:22:14.641 >> DMON Process Shutdown <<
03/17/2016 09:23:49
>> Starting Data Guard Broker bootstrap <<
Broker Configuration File Locations:
dg_broker_config_file1 = "/oracle/app/oracle/product/db/12.1.0.2/dbs/dr1dgdb.dat"
dg_broker_config_file2 = "/oracle/app/oracle/product/db/12.1.0.2/dbs/dr2dgdb.dat"
2016-03-17 09:23:52.438 DMON: Boot configuration (0.0.0), loading from "/oracle/app/oracle/product/db/12.1.0.2/dbs/dr1dgdb.dat"
2016-03-17 09:23:52.439 DMON: FSFO - observer ping countdown timer - oTime reset to current time
2016-03-17 09:23:52.439 Database needs to be reinstated or re-created, Data Guard broker ready <<<<<<<<
2016-03-17 09:23:52.439 7fffffff 0 DMON: Entered rfm_release_chief_lock() for CTL_BOOTSTRAP
2016-03-17 10:26:51.410 Data Guard Broker shutting down

 

Changes

 New environment

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.