Opmnctl Startall fails with Failed To Start a Process Because A Dependency Check Failed

OID is not running or unavailable

Subject: opmnctl Startall fails with Failed To Start a Process Because A Dependency Check Failed

Cause

A midtier attached to an infrastructure has by default the dependency of OID declared in opmn.xml, but it can be removed without any risk if OID is not used by these OC4J instances.

The OID dependency is just needed if JAZN-LDAP or SSO authentication methods have been setup.

Solution
-- To implement the solution, please execute the following steps::

1) Backup the file $ORACLE_HOME/opmn/conf/opmn.xml
2) Edit $ORACLE_HOME/opmn/conf/opmn.xml and locate the lines:


<ias-component id="OC4J">
<dependencies>
<OID infrastructure="true"/>
</dependencies>
<process-type id="home" module-id="OC4J" status="disabled">
<module-data>
<category id="start-parameters">


3) Remove the lines:


<dependencies>
<OID infrastructure="true"/>
</dependencies&gt


i.e. the section will become:

<ias-component id="OC4J">

<process-type id="home" module-id="OC4J" status="disabled">
<module-data>
<category id="start-parameters">;


4) Save the file
5) Run the commands:

$ORACLE_HOME/opmn/bin/opmnctl stopall
$ORACLE_HOME/opmn/bin/opmnctl startall

Source : Oracle Metalink Doc ID: Note:401882.1