Oracle Clusterware Cannot Start on all Nodes: Network communication with node <NAME> missing for 90% of timeout interval
(Doc ID 1507482.1)
Last updated on DECEMBER 25, 2019
Applies to: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
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
This note is a troubleshooting guide for the following situation: Oracle Clusterware cannot be started on all nodes at once. For example, in a 2-node cluster, the Oracle Clusterware on the 2nd node won't start, or, attempting to start clusterware on the second node causes the first node's clusterware to shutdown.
In the clusterware alert log ($GRID_HOME/log/<hostname>/alert<hostname>.log) of one or more nodes where Oracle Clusterware is started, the following messages are seen:
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
|Step 1. Basic connectivity:|
|Step 2. After basic connectivity is confirmed, check advanced connectivity checks:|
|Step 3. Known bugs|