CRS Does not Start After Power Outage - NS err (12603, 12560), transport (530, 1, 0)
(Doc ID 1467647.1)
Last updated on SEPTEMBER 16, 2021
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 to 126.96.36.199 [Release 10.2 to 11.1]
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
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.
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