Wrong start options values for database config after Data Guard switchover shown in srvctl (Doc ID 1939968.1)

Last updated on APRIL 06, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.1.0.1 [Release 11.2 to 12.1]
Information in this document applies to any platform.

Symptoms

srvctl shows incorrect "Start Options" upon performing physical data guard switchover from primary to active standby (ADG).

New standby:
Start options: open
Database role: PHYSICAL_STANDBY

New primary:
Start options: read only
Database role: PRIMARY

 

Changes

Performed a switchover from Primary to standby. The "Start option" is not updated correctly.

Pre-switchover:

$ srvctl config database -d db1
Database unique name: db1
Database name: db1
...
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
...
Type: RAC
...
Database is policy managed

$ srvctl config database -d db2
Database unique name: db2
Database name: db1
....
Start options: read only
Stop options: immediate
Database role: PHYSICAL_STANDBY
Management policy: AUTOMATIC
...
Type: RAC
...
Database is policy managed

Peformed a switchover using dgmgrl.

Post switch-over:

$ srvctl config database -d db1
Database unique name: db1
Database name: db1
...
Start options: open  <<<<<<<<<<<<<<<<<<<<<<<<<Start option did not update correctly
Stop options: immediate
Database role: PHYSICAL_STANDBY
Management policy: AUTOMATIC
...
Type: RAC
..
Database is policy managed


$ srvctl config database -d db2
Database unique name: db2
Database name: db1
...
Start options: read only <<<<<<<<<<<<<<<<<<<<<<Start option did not update correctly
Stop options: immediate 
Database role: PRIMARY
Management policy: AUTOMATIC
....
Type: RAC
...
Database is policy managed

 

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