Unable to Kill Orphan Process. Opmnctl Shows Essbase Status as Stop

(Doc ID 1911011.1)

Last updated on AUGUST 02, 2017

Applies to:

Hyperion Essbase - Version and later
Information in this document applies to any platform.


An orphaned Essbase process is shown with Essbase status as Stop and pid is not the Essbase process. It is an unrelated process.

Output for opmnctl status-

There is no process with ID 9976 is running under Hyperion user.

Opmn.log error:

[2014-07-21T09:37:35+02:00] [opmn] [NOTIFICATION:1] [668] [pm-requests] Request 6 Completed. Command: /stop
[2014-07-21T09:37:35+02:00] [opmn] [NOTIFICATION:1] [663] [pm-process] Stopping Process: EssbaseCluster-2~EssbaseAgent~AGENT~50 (1470912965:9976)
[2014-07-21T09:37:35+02:00] [opmn] [ERROR:1] [] [libopmness] Forcefully Terminating Process: EssbaseCluster-2~EssbaseAgent~AGENT~50 (1470912965:9976)
[2014-07-21T09:37:35+02:00] [opmn] [NOTIFICATION:1] [667] [pm-requests] Request 7 Started. Command: /shutdown

 console~Essbase1~EssbaseAgent~AGENT~1 .log error:

Error in Mon Jul  7 16:44:03 2014]Local/ESSBASE0///139852386043632/Error(1042010) Network Error [98]: Failed to bind a host server socket on port[1424]
Fatal Error: Error initializing network


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms