opmnctl opmn is not running and failed to start a managed process after the maximum retry limit.

opmnctl opmn is not running| In this post describe how to resolve the opmnctl opmn  failed to start a managed process after the maximum retry limit issue.

Opmnctl opmn is not running.

Scenario:

Recently we have got error ‘Failed to start managed process after the maximum retry limit’ because copied IAS from different machine and 
try to start the opmn service as below.

Error : oracle opmn start failed . We can check the opmn logs to check opmn is not running.

======

[oracle@appsprd ~]$ opmnctl startall

opmnctl: starting opmn and all managed processes…

opmn id=doyen.com:6299

    0 of 1 processes started.

ias-instance id=standalone

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

ias-component/process-type/process-set:

    HTTP_Server/HTTP_Server/HTTP_Server

Error:

–> Process (pid=10533)

    failed to start a managed process after the maximum retry limit

    Log:

    /data01/apex/prd/opmn/logs/HTTP_Server~1

Solution:

[oracle@appsprd ~]$ su – root

Password:

[root@appsprd oracle]# ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2

Now Retest the issue : In my case issue got resolved.

=====================

[oracle@appsprd ~]$ opmnctl startall

opmnctl: starting opmn and all managed processes…

[oracle@appsprd ~]$ ./opmnctl status

Processes in Instance: apex_home. appsprd.com

——————-+——————–+———+———

ias-component      | process-type       |     pid | status

——————-+——————–+———+———

DSA                    | DSA                           |     N/A | Down

LogLoader          | logloaderd                 |     N/A | Down

dcm-daemon      | dcm-daemon             |     N/A | Down
OC4J                  | home                          |    5678 | Alive
HTTP_Server    | HTTP_Server            |    5677 | Alive

1 thought on “opmnctl opmn is not running and failed to start a managed process after the maximum retry limit.”

Leave a Comment