Oracle Grid Infrastructure: How to Troubleshoot Node Reboots/Evictions or Abrupt Recycle of CRS due to the Escalation of a Member Kill Request to a Node Kill Request
(Doc ID 1549977.1)
Last updated on DECEMBER 31, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 and laterOracle 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
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Purpose
When an evicted instance does not abort, the member kill request is sent to the ocssd.bin daemon of CRS of the node with the problem instance. If the ocssd.bin daemon can not abort the problem instance in 30 seconds, the member kill request is escalated to the node kill request.
The result of the node kill request is that the node is rebooted unless CRS shuts down gracefully.
Troubleshooting Steps
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
| Purpose |
| Troubleshooting Steps |
| References |