11g-crsctl_start_crs-failed-workaround

SYMPTOMS

crsctl start crs

CRS-4124: Oracle High Availability Services start failed

CAUSE：
Install of Clusterware fails while running root.sh on OL7 - ohasd fails to start (Doc ID 1959008.1)

In OL7 it needs to be set up as a service and patch fix for Bug 18370031 needs to be applied for this , BEFORE you run root.sh when prompted .
Need to apply the patch 18370031 for 11.2.0.4 .
And also its mentioned in 11gR2 Release Notes:https://docs.oracle.com/cd/E11882_01/relnotes.112/e23558/toc.htm#CJAJEBGG

WORKAROUND:

Clear all sockets under /var/tmp/.oracle or /tmp/.oracle if any and then open two terminals of the same node, where stack is not coming up.

  1. On Terminal 1 , issue as Root user :
    crsctl start crs

  2. Simultaneously , open another terminal of the same node and issue the below command as Root user once the npohasd socket has been created.
    /bin/dd if=/var/tmp/.oracle/npohasd of=/dev/null bs=1024 count=1

  3. Now if you check on terminal 1 , the CRS stack would start coming up.

ps -ef |grep d.bin

  1. Once entire CRS stack is up, you can press CTRL+C and come out of the dd command running on 2nd terminal.

Check and validate all resources are online using

crsctl stat res -t
crsctl stat res -t -init

WORKAROUND-2

----workaround-2: add ohas.service in rac-host1 and rac-host2

vi /usr/lib/systemd/system/ohas.service

[Unit]
Description=Oracle High Availability Services
After=syslog.target

[Service]
ExecStart=/etc/init.d/init.ohasd run >/dev/null 2>&1 Type=simple
Restart=always

[Install]
WantedBy=multi-user.target

systemctl daemon-reload
systemctl enable ohas.service
systemctl start ohas.service

systemctl status ohas.service

crsctl start crs

参考文档：
https://www.modb.pro/db/25739
Install of Clusterware fails while running root.sh on OL7 - ohasd fails to start (Doc ID 1959008.1)
Cluster Failed to Start Due to Problem With Socket Pipe npohasd (Doc ID 1612325.1)

posted @ 2023-10-09 15:20  武汉OracleDBA  阅读(15)  评论(0)  编辑  收藏  举报