Top 5 Issues That Cause Node Reboots or Evictions or Unexpected Recycle of CRS
(Doc ID 1367153.1)
Last updated on JULY 19, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata 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
Information in this document applies to any platform.
This note is a short summary of top issues that cause node reboots or unexpected recycle of CRS
All users with node reboot issues
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
|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|