Cluster Services Not Up On One Node
(Doc ID 2677266.1)
Last updated on SEPTEMBER 29, 2021
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Two nodes cluster. Node 2 is up and running. Node 1 is not coming up.
cluster alert.log from node 1:
2020-05-22 13:07:36.157 [OCSSD(83574)]CRS-1713: CSSD daemon is started in hub mode
2020-05-22 13:07:41.885 [OCSSD(83574)]CRS-1656: The CSS daemon is terminating due to a fatal error; Details at (:CSSSC00012:) in /u01/app/oracle/diag/crs/xxxx/crs/trace/ocssd.trc
2020-05-22 13:07:41.917 [OCSSD(83574)]CRS-1652: Starting clean up of CRSD resources.
2020-05-22 13:07:41.925 [OCSSD(83574)]CRS-1653: The clean up of the CRSD resources failed.
2020-05-22 13:07:44.941 [OCSSD(83574)]CRS-8503: Oracle Clusterware process OCSSD with operating system process ID 83574 experienced fatal signal or exception code 6.
Errors in file /crs/trace/ocssd.trc (incident=425):
CRS-8503            
Incident details in: /crs/incident/incdir_425/ocssd_i425.trc
2020-05-22 13:07:40.863 : SKGFD:998745856: ERROR: -8(OS Error -1 (open,sskgxplp,Invalid protocol requested (2) or protocol not loaded.,Error 0) >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> OS error
2020-05-22 13:07:40.863 : SKGFD:998745856: ERROR: -10(OSS Operation oss_initialize failed with error 4 [Network initialization failed]
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