We have
two-node primary RAC database & two-node standby RAC database. For the
business testing purpose, they will want both side of the database in the READ
WRITE Mode. So we have decided to disabled the log shipping and made the
standby database as a new primary database using failover database.
During
the standby failover process, we made the existing primary database down. We
have successfully failover the standby database as a new primary database. Once
the process completed, we have disabled the DG configuration.
When we
try to start the old primary database, we go the below error message. After analyzing
further, we found the DG configuration file has been update from the standby
database DG configuration file. Since the standby database become a new
primary. So it has update the DG configuration file in the old primary
database.
ORA-16649: possible failover to another
database prevents this database from being opened
SOLUTION
After
disabling the DG_BROKER_START=FALSE; the
old primary database able to start in the READ WRITE mode.
SQL> startup force
ORACLE instance
started.
Total System Global
Area 7.2958E+10 bytes
Fixed Size 2235808 bytes
Variable Size 1.9059E+10 bytes
Database
Buffers 5.3687E+10 bytes
Redo Buffers 209866752 bytes
Database mounted.
ORA-16649: possible failover to another database prevents
this database from being opened
SQL> select database_role from v$database;
DATABASE_ROLE
----------------
PRIMARY
SQL> alter system set dg_broker_start=false scope=both
sid='*';
System altered.
SQL> alter database open;
Database altered.
