Grid Infrastructure (GI) Crashes and Fails to Start After "/var/tmp" Directory Was Removed as ohasd Can Not Create Named Pipe
(Doc ID 1567797.1)
Last updated on APRIL 12, 2024
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
11gR2 Grid Infrastructure crashes and can not start, "crsctl start crs" reports:
OHASD START FAILS WITH ERROR CREATING THE NAMED PIPE
In certain situations, Clusterware startup error with below lines logged in alert log
alertracnode1.log (inside <Grid Infrastructure Home>/log/<host name>/ohasd):
2018-06-10 15:38:24.534
[client(15165)]CRS-2101:The OLR was formatted using version 3.
2018-06-10 15:38:25.134
[client(15201)]CRS-1001:The OCR was formatted using version 3.
[client(15276)]CRS-10001:CRS-6021: No msg for has:crs-6021 [l][unlimited]
[client(15165)]CRS-2101:The OLR was formatted using version 3.
2018-06-10 15:38:25.134
[client(15201)]CRS-1001:The OCR was formatted using version 3.
[client(15276)]CRS-10001:CRS-6021: No msg for has:crs-6021 [l][unlimited]
ohasdOUT.log indicates error creating the named pipe
ohasdOUT.log (inside <Grid Infrastructure Home>/log/<host name>/ohasd):
OHASD stderr redirected to ohasdOUT.log
2018-06-10 15:38:31
Changing directory to <GI_HOME>/log/<NODE>/ohasd
OHASD starting
Error creating the named pipe: Permission denied
2018-06-10 15:38:31
Changing directory to <GI_HOME>/log/<NODE>/ohasd
OHASD starting
Error creating the named pipe: Permission denied
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 |
Cause |
Solution |