Unable to Kill Orphan Process. Opmnctl Shows Essbase Status as Stop
(Doc ID 1911011.1)
Last updated on OCTOBER 01, 2019
Applies to:Hyperion Essbase - Version 220.127.116.11.500 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] [NOTIFICATION:1] [pm-requests] Request 6 Completed. Command: /stop
[opmn] [NOTIFICATION:1] [pm-process] Stopping Process: EssbaseCluster-2~EssbaseAgent~AGENT~50 (9976)
[opmn] [ERROR:1]  [libopmness] Forcefully Terminating Process: EssbaseCluster-2~EssbaseAgent~AGENT~50 (9976)
[opmn] [NOTIFICATION:1]  [pm-requests] Request 7 Started. Command: /shutdown
console~Essbase1~EssbaseAgent~AGENT~1 .log error:
Local/ESSBASE0/Error(1042010) Network Error : Failed to bind a host server socket on port
Fatal Error: Error initializing network
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