Solaris: Grid Infrastructure Startup Slow Due CSSD Voting Disk Discovery (may cause root.sh failure)
(Doc ID 1451367.1)
Last updated on MAY 14, 2021
Applies to:Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
When installing 220.127.116.11 Grid Infrastructure (or upgrading from an earlier 11.2 patchset) on Solaris (SPARC and x86-64) systems having large numbers of disks CSSD can take excessive time in Voting Disk discovery resulting in CSSD timing out during startup. This will will cause the failure of root.sh (or rootupgrade.sh). When this happens the following symptoms are generally present:
- Excessive time spent during ASMCA execution
- root.sh or rootupgrade.sh failures due to cssd startup timeout (10 minutes)
This issue may also impact existing 18.104.22.168 installations where Grid Infrastructure startup is extremely slow on Solaris and again the system has a large number of disks.
- Slow GI startup due to CSSD Voting Disk discovery (assuming successful root.sh execution)
- Slow queries on v$asm_disk from 22.214.171.124 ASM (assuming successful root.sh execution on a node)
- "Alter database open" takes long time
To verify that Oracle CSS daemon startup is timing out due to Voting Disk discovery, the ocssd.log file (located under $GRID_HOME/log/<nodename>/cssd/ocssd.log) and the cssdagent_root.log (located under $GRID_HOME/log/<nodename>/agent/ohasd/cssdagent_root/cssdagent_root.log) must be reviewed. In case the case of a root.sh/rootupgrade.sh failure the rootcrs_<nodename>.log (located under $GRID_HOME/cfgtoollogs/crsconfig/rootcrs_<nodename>.log) should also be reviewed to ensure the failure was caused by a CSSD startup timeout. Below are snipits of the mentioned logs describing the issue:
rootcrs_<nodename>.log (Applies to Install or Upgrade Failures ONLY):
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