Top 5 Issues That Cause Node Reboots or Evictions or Unexpected Recycle of CRS
(Doc ID 1367153.1)
Last updated on DECEMBER 09, 2024
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterGen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database 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
This note is a short summary of top issues that cause node reboots or unexpected recycle of CRS.
Scope
All users with node reboot issues
Details
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 |
| Scope |
| Details |
| Issue #1: The node rebooted, but the log files do not show any error or cause. |
| Issue #2: The node rebooted because it was evicted due to missing network heartbeats. |
| Issue #3: The node rebooted after a problem with storage. |
| Issue #4: Node is rebooted after asm or database instance hang or eviction. |
| Issue #5: The CRS recycled automatically, but node did not reboot |
| References |