Top 5 Grid Infrastructure Startup Issues
(Doc ID 1368382.1)
Last updated on APRIL 20, 2020
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.
The purpose of this note is to provide a summary of the top 5 issues that may prevent the successful startup of the Grid Infrastructure (GI) stack.
This note applies to 11gR2 Grid Infrastructure only.
To determine the status of GI, please run the following commands:
2. $GRID_HOME/bin/crsctl stat res -t -init
3. $GRID_HOME/bin/crsctl stat res -t
4. ps -ef | egrep 'init|d.bin'
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: CRS-4639: Could not contact Oracle High Availability Services, ohasd.bin not running or ohasd.bin is running but no init.ohasd or other processes|
|Issue #2: CRS-4530: Communications failure contacting Cluster Synchronization Services daemon, ocssd.bin is not running|
|Issue #3: CRS-4535: Cannot communicate with Cluster Ready Services, crsd.bin is not running|
|Issue #4: Agent or mdnsd.bin, gpnpd.bin, gipcd.bin not running|
|Issue #5: ASM instance does not start, ora.asm is OFFLINE|