Problems with Oracle Data Guard Role Transitions
The following solutions apply to problems with role transitions (failover, reinstate, and switchover) in an Oracle Database Classic Cloud Service deployment hosting an Oracle Data Guard configuration.
A message in the Activity area indicates that the reinstate operation failed
"Successfully Reinstated" is displayed after the reinstate, but the Activity area on the Overview page indicates that the reinstate operation failed.
Perform the following steps to resolve this discrepancy:
-
On the Database Service console Overview page, click the Refresh Configuration icon.
-
Refresh the Overview page.
-
Click the Refresh Configuration icon again and observe that the Database Role has changed from Reinstate to Standby.
You can ignore the message in the Activity area indicating that the reinstate failed.
A message indicates a problem with the SYS password on the standby database
If you did not use the database changepassword
subcommand of the dbaascli
utility to change the password of the SYS
user in your Oracle Data Guard configuration, the password file on the standby database may not have been updated correctly. See Changing the SYS Password for detailed information on changing the SYS
user’s password.
After a role transition operation, I get an ORA-16792 warning when I check the status of the configuration
After attempting a role transition, both the DGMGRL SHOW CONFIGURATION
command and the dbaascli dataguard status
command report the warning: "ORA-16792: configurable property value is inconsistent with database setting."
Perform the following steps to resolve the inconsistent setting warning:
-
Connect as the
oracle
user to the compute node hosting the primary database. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). -
Invoke DGMGRL.
$ dgmgrl /
-
Use the DGMGRL
SHOW DATABASE
command to determine which Data Guard broker property is inconsistent with the database setting.DGMGRL> SHOW DATABASE 'database-name' 'InconsistentProperties';
Where
database-name
is the name of the primary database (SID).For example:
DGMGRL> SHOW DATABASE 'ORCL' 'InconsistentProperties'; INCONSISTENT PROPERTIES INSTANCE_NAME PROPERTY_NAME MEMORY_VALUE SPFILE_VALUE BROKER_VALUE ORCL ArchiveLagTarget 0 0
-
Use the DGMGRL
EDIT DATABASE
command to reset the Data Guard broker property value, which in turn sets the value in the server parameter file (SPFILE).DGMGRL> EDIT DATABASE 'database-name' SET PROPERTY 'property-name'=value;
Where:-
database-name
is the name of the database (SID) -
property-name
is the name of the Data Guard broker property displayed in the output from theSHOW DATABASE
command -
value
is the value displayed inMEMORY_VALUE
in the output from theSHOW DATABASE
command.
For example:
DGMGRL> EDIT DATABASE 'ORCL' SET PROPERTY 'ArchiveLagTarget'=0; Property "ArchiveLagTarget" updated
-
-
Exit from DGMGRL and close your connection to the compute node.