The engine log will show messages similar to the following for the oacore resource:
ffdc:20059:
VCS monitors the resources by looking for particular processes and their agruments in the process table. The argument list for OracleApp resources can be very long and it is possible for the process table to truncate the process, meaning some arguments are not shown in the process table. This means that VCS monitoring can not find the running process and so monitors the resource to be offline.
Edit the opmn.xml file to reduce the argument list length. This means the particular arguments VCS is looking for will now appear in the process table and so the resource will be monitored as online.
For example, in this case the oacore java.policy and jazn.xml files are moved to a different location, this means the path is reduced. In the opmn.xml file the 'java-options' line for that process-type can then be adjusted as follows:
-Djava.security.policy=$ORACLE_HOME/j2ee/oacore/config/java2.policy
-Doracle.security.jazn.config=/oraaps/oracle/PROD/inst/apps/PROD_app1/ora/10.1.3/j2ee/oacore/config/jazn.xml
to
-Djava.security.policy=/oraaps/oracle/oacore/java2.policy
-Doracle.security.jazn.config=/oraaps/oracle/oacore/jazn.xml
Applies To
OracleApps resources under VCS control.