Exalytics: Essbase Server is Down and OPMNCTL Command Fails with Error: "Failed to Start a Managed Process after the Maximum Retry Limit"

(Doc ID 1952430.1)

Last updated on OCTOBER 23, 2017

Applies to:

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


The Essbase server on Exalytics is down and cannot be restarted.  When running opmnctl command, if fails with error shown below:

[essbase@servername bin]$ ./opmnctl status

Processes in Instance: EPM_epmsystem1
ias-component | process-type | pid | status
Essbase1 | EssbaseAgent | N/A | Down

[essbase@servername bin]$ ./opmnctl startall
opmnctl startall: starting opmn and all managed processes...
opmn id=servername.domain:6712
Response: 0 of 1 processes started.

ias-instance id=EPM_epmsystem1

--> Process (index=1,uid=1720780554,pid=22420)
 failed to start a managed process after the maximum retry limit


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