Stopping GI on a Single Node Results in Complete Database Outage
(Doc ID 2765024.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 and laterInformation in this document applies to any platform.
Symptoms
When Oracle Clusterware is stopped on one node (Manual Shutdown or via Patching) of a multi-node system having a RAC database, the expectation is that ONLY the database instance local to the system where Clusterware is being stopped will shutdown leaving the remaining database instances available to service the application workload. In some cases it has been found that the Clusterware shutdown on one node leads to a complete database outage (all instances are shutdown).
Changes
ASM Diskgroup mounted for temporary purposes AND/OR Removed from a given cluster after being mounted by a database.
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 |