CRS Does not Start After Power Outage - NS err (12603, 12560), transport (530, 1, 0)

(Doc ID 1467647.1)

Last updated on FEBRUARY 06, 2018

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 10.2 to 11.1]
Information in this document applies to any platform.


3 node RAC cluster, after power outage, CRS could no longer be started on any of the node. All 3 processes (ocssd.bin, crsd.bin and evmd.bin) are running:

$ ps -ef | grep d.bin
oracrs    6934  6931  0 13:58 ?        00:00:00 /u01/crs//bin/evmd.bin
root      6959 13621  0 13:58 ?        00:00:00 /u01/crs/bin/crsd.bin reboot
oracrs    8206  7078  0 13:58 ?        00:00:01 /u01/crs/bin/ocssd.bin


$ crsctl check crs get:

CRS-0184 Cannot communicate with the CRS daemon.

Further check shows CSSD has not formed the cluster:

CRS could not start even just start CRS on 1 node only with the other two nodes down. Ping and traceroute work fine for all nodes private network.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms