Services are Running on Wrong RAC Instances
(Doc ID 965385.1)
Last updated on SEPTEMBER 09, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 10.2.0.4 [Release 10.1 to 10.2]
Oracle Database Cloud Schema 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
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
On a 4 node RAC cluster, database services are running on the wrong instances after instance restart.
Consider the following service configuration:
<DATABASE_NAME3> PREF: <INSTANCE1> <INSTANCE2> AVAIL: <INSTANCE3> <INSTANCE4>
<DATABASE_NAME2> PREF: <INSTANCE2> AVAIL: <INSTANCE1>
The service '<DATABASE_NAME2>' was running on all 4 instances when it should have been running on instance 2 (<INSTANCE2>) only.
This caused user sessions to be connected to the wrong instances, leading to load problems.
The same happened for another service (<DATABASE_NAME3>).
All instances had been restarted during maintenance window.
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