Solaris Cluster's Oracle DB resource not starting because of Data Gaurd role change
(Doc ID 2724091.1)
Last updated on SEPTEMBER 01, 2023
Applies to:
Solaris Cluster - Version 4.0 to 4.4 [Release 4.0 to 4.4]Information in this document applies to any platform.
Symptoms
Oracle Database resource logs the following errors during a start.
When there is a mismatch between Oracle Database role and the SUNWScor parameter, the following errors could be logged:
SC[SUNWscor.oracle_server.start]: RG1:RS1: [ID 635928 daemon.error] Role change from PRIMARY to PHYSICAL STANDBY detected.
SC[SUNWscor.oracle_server.start]:RG1:RS1: [ID 128754 daemon.error] The dataguard settings of the \
Oracle Solaris Cluster resource appear to be incorrect and do not match the values of the Oracle database.
Cluster.RGM.global.rgmd: [ID 938318 daemon.error] Method <bin/oracle_server_start> failed on resource <RS1> in resource \
group <RG1> [exit code <1>, time used: 15% of timeout <600 seconds>]
SC[SUNWscor.oracle_server.start]: RG1:RS1: [ID 635928 daemon.error] Role change from PRIMARY to PHYSICAL STANDBY detected.
SC[SUNWscor.oracle_server.start]:RG1:RS1: [ID 128754 daemon.error] The dataguard settings of the \
Oracle Solaris Cluster resource appear to be incorrect and do not match the values of the Oracle database.
Cluster.RGM.global.rgmd: [ID 938318 daemon.error] Method <bin/oracle_server_start> failed on resource <RS1> in resource \
group <RG1> [exit code <1>, time used: 15% of timeout <600 seconds>]
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 |
| Cause |
| Solution |
| References |