My Oracle Support Banner

Troubleshooting Clusterware Node Evictions (Reboots) (Doc ID 1050693.1)

Last updated on JANUARY 28, 2024

Applies to:

Solaris Operating System - Version 11.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - 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 document is to provide a reference for troubleshooting Clusterware node evictions in versions 11.2 and above.  For clusterware node evictions prior to 11.2, see <Note: 265769.1>

Scope

This document is intended for DBA's and support analysts experiencing clusterware node evictions (reboots).

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
 NODE EVICTION OVERVIEW
 1.0 - PROCESS ROLES FOR REBOOTS
 2.0 - DETERMINING WHICH PROCESS IS RESPONSIBLE FOR A REBOOT
 3.0 - TROUBLESHOOTING OCSSD EVICTIONS
 3.1 - COMMON CAUSES OF OCSSD EVICTIONS
 3.2 - FILES TO REVIEW AND GATHER FOR OCSSD EVICTIONS
 4.0 - TROUBLESHOOTING CSSDAGENT OR CSSDMONITOR EVICTIONS
 4.1 - COMMON CAUSES OF CSSDAGENT OR CSSDMONITOR EVICTIONS
 4.2 - FILES TO REVIEW AND GATHER FOR CSSDAGENT OR CSSDMONITOR EVICTIONS
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.