CRS-41053: checking Oracle Grid Infrastructure for file permission issues. Not Able To Start HAS after patching failure. (Doc ID 2894422.1)

Last updated on APRIL 17, 2023

Applies to:

Symptoms

The HAS was failing to startup with the following message:

3) No messages were reported in the ohasd.trc file

4) No errors were reported in the OS logs, located under var/log called messages. (For Linux)

5) Rebooting the node didn't start up the HAS even though the auto-start feature was enabled.

6) The directory permission on the inventory.xml file location and it's parent directory were incorrect but even after fixing the permissions, it didn't help with bringing the HAS online.

7) The CRS failed to come online even after executing roothas.sh -lock or roothas.sh -patch

Changes

After manual intervention during a failed patching process, the CRS was failing to startup

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.