Services With Role Set to Primary Are Started Even When The Role is Standby
(Doc ID 2215197.1)
Last updated on AUGUST 20, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 to 12.1.0.2 [Release 11.2 to 12.1]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
o RAC Dataguard configuration using a Physical Standby managed with the DG broker.
o Service was created with role set to Primary:
Service name: myserv
Service is enabled
Server pool:
Cardinality: 1
Disconnect: false
Service role: PRIMARY <<<< ROLE >>>>>
...
o After a switchover, the service still running even when the role was set to PHYSICAL_STANDBY on the database:
$srvctl status service -d <DB_NAME> -s myserv
Service <service_name> is running on instance(s) <instance_name>
Service <service_name> is running on instance(s) <instance_name>
here are the roles for the database and service, using 'crsctl stat res -f':
...
NAME=ora.<db_name>.db
..
ROLE=PHYSICAL_STANDBY
..
NAME=ora.<db_name>.myserv.svc
..
ROLE=PRIMARY
NAME=ora.<db_name>.db
..
ROLE=PHYSICAL_STANDBY
..
NAME=ora.<db_name>.myserv.svc
..
ROLE=PRIMARY
Changes
Using DG broker to manage the DG configuration
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 |
| References |