My Oracle Support Banner

Unable to start OHASD after apply of PSU patch. (Doc ID 1562797.1)

Last updated on FEBRUARY 21, 2024

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

After PSU patch in Grid home, OHASD failed to start

The errors reported will vary depending on Oracle version and PSU.

For 11.2.0.1, you may see:

CLSU-00100: Operating System function: waitpid failed with error data: 0
CLSU-00101: Operating System error message: Error 0
CLSU-00103: error location: usrgetgrp12
CLSU-00104: additional error information: child returned 232

CRS-4000: Command Start failed, or completed with errors.
Timed out waiting for ohasd to start.

Then ohasd start timed out after a while ,

2013-06-13 12:29:45: Checking the status of ohasd
2013-06-13 12:29:50: Executing cmd: <Grid Infrastructure Home>/bin/crsctl check has
2013-06-13 12:29:51: Checking the status of ohasd
2013-06-13 12:29:56: Executing cmd: <Grid Infrastructure Home>/bin/crsctl check has
2013-06-13 12:29:58: Checking the status of ohasd
2013-06-13 12:30:03: Timed out waiting for ohasd to start.

 

For Oracle 12c, ohasd.log will reflect messages similar to:

 

For orarootagent:

2014-12-17 20:58:25.721: [    AGFW][967866112] {0:0:2} Starting the agent: <Grid Infrastructure Home>/bin/orarootagent with user id: root and incarnation:1
2014-12-17 20:58:25.721: [    AGFW][967866112] {0:0:2} Created alert : (:CRSAGF00123:) :  Failed to start the agent process: <Grid Infrastructure Home>/orarootagent Category: -1 Operation: fail Loc: canexec2 OS error: 0 Other : no exe permission, file [<Grid Infrastructure Home>/orarootagent]
2014-12-17 20:58:25.722: [    AGFW][967866112] {0:0:2} Created alert : (:CRSAGF00126:) :  Agent start failed

For oraagent:

2014-12-17 20:58:25.723: [    AGFW][967866112] {0:0:2} Starting the agent: <Grid Infrastructure Home>/oraagent with user id: grid and incarnation:1
2014-12-17 20:58:25.727: [    AGFW][967866112] {0:0:2} Created alert : (:CRSAGF00123:) :  Failed to start the agent process: <Grid Infrastructure Home>/oraagent Category: -2 Operation: waitpid Loc: usrgetgrp12 OS error: 0 Other : child returned 232
2014-12-17 20:58:25.727: [    AGFW][967866112] {0:0:2} Created alert : (:CRSAGF00126:) :  Agent start failed

For cssdagent:

2014-12-17 20:58:25.732: [    AGFW][967866112] {0:0:2} Starting the agent: <Grid Infrastructure Home>/cssdagent with user id: root and incarnation:1
2014-12-17 20:58:25.732: [    AGFW][967866112] {0:0:2} Created alert : (:CRSAGF00123:) :  Failed to start the agent process: <Grid Infrastructure Home>/cssdagent Category: -1 Operation: fail Loc: canexec2 OS error: 0 Other : no exe permission, file [<Grid Infrastructure Home>/cssdagent]
2014-12-17 20:58:25.732: [    AGFW][967866112] {0:0:2} Created alert : (:CRSAGF00126:) :  Agent start failed

For cssdmonitor:

2014-12-17 20:58:25.733: [    AGFW][967866112] {0:0:2} Starting the agent: <Grid Infrastructure Home>/cssdmonitor with user id: root and incarnation:1
2014-12-17 20:58:25.733: [    AGFW][967866112] {0:0:2} Created alert : (:CRSAGF00123:) :  Failed to start the agent process: <Grid Infrastructure Home>/cssdmonitor Category: -1 Operation: fail Loc: canexec2 OS error: 0 Other : no exe permission, file [<Grid Infrastructure Home>/cssdmonitor]
2014-12-17 20:58:25.734: [    AGFW][967866112] {0:0:2} Created alert : (:CRSAGF00126:) :  Agent start failed

 

Changes

 

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


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