OID Component Fails To Start on Oracle Solaris ERROR: "Error occurred while performing nmStart : Error Starting server oid1: Received error message from Node Manager Server: [Server start command for OID" (Doc ID 2948553.1)

Last updated on MAY 17, 2023

Applies to:

Symptoms

OID component fails to start on Oracle Solaris SPARC when the OS was restarted after completing patching for the April 2023 CPU. 

Error:

Error occurred while performing nmStart : Error Starting server oid1 : Received error message from Node Manager Server: [Server start command for OID server 'oid1' failed due to: [Server failed to start up but Node Manager was not aware of the reason]. Please check Node Manager log and/or server 'oid1' log for detailed information.]. Please check Node Manager log for details.

The results from ps -ef | grep oid[dlm] showed a running PID for the oidmon process only. No processes for oidldapd or oiddispd are running. 

The ods_process_status table in the oid database shows the PID=0 and the State=1. 

Attempts to terminate the running oidmon process and reset the State=4 in the ods_process_status table failed to resolve the issue and oid component still does not start. 

There are also multiple stack dump logs generated for the oidmon process which indicates failures with the oidmon during 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.