ASM not starting on NON-first node and OHASD rootagent logs says "Error 4 opening dom ASM/Self"
(Doc ID 2880705.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 19.15.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
ASM on node 2 is not starting after node addition . root.sh is failing with below error .
root.sh
======
CRS-4123: Oracle High Availability Services has been started.
2022/06/14 12:54:27 CLSRSC-12: The ASM resource ora.asm did not start
2022/06/14 12:54:27 CLSRSC-117: Failed to start Oracle Clusterware stack from the Grid Infrastructure home <GRID_HOME>
2022/06/14 12:54:27 CLSRSC-12: The ASM resource ora.asm did not start
2022/06/14 12:54:27 CLSRSC-117: Failed to start Oracle Clusterware stack from the Grid Infrastructure home <GRID_HOME>
Changes
ASM on node 2 is not starting
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |