Step by Step resolution for the problem oacore not coming up in R12

Last updated on September 21st, 2017 at 05:20 pm

I would be presenting some solutions for oacore not coming up  in R12 EBS  version.

First let me give brief idea about oacore mechanism in R12

In R12 we have 3 groups of OC4J’s.

oacore OC4J – Supports framework based applications
forms OC4J – Supports forms based applications
oafm OC4J – expands to Oracle Application Fusion Middleware – for mapviewer, webservices, ascontrol

R12 OC4J processes  are managed by OPMN(Oracle Process Manager and Notification Server). OPMN consists of two main components (Oracle Process Manager) and (Oracle Notification Server).

Oracle Process Manager is responsible for
1) starting
2) stopping
3) restarting
4) monitoring the services it manages (this includes death detection and automatic restart of the process)

Oracle Notification Server is the transport mechanism for failure, recovery, startup, and other related notifications between components in AS.

Single configuration file(opmn.xml) is used OPMN to manage the services. Config file location is given as $ORA_CONFIG_HOME/10.1.3/opmn/conf/opmn.xml

What algorithm OPMN uses to detect the death?

1) OS process is checked by OPMN for every 2 seconds.
2) forward ping: periodically OPMN pings the process for every 20 seconds and expects response
3) reverse ping: every 20 seconds managed process sends OPMN a ping notification

Now let’s see the resolution for the problem  oacore not starting Up

Various errors could be for oacore not coming up – ERROR : Timed out( 100000 ): Interrupted Exception exiting with status 204 & exiting with status 150

Reason for oacore not coming up

There could be various reason for the problem

a) IP address change

b) resource bottleneck


Solution for oacore not coming up

We can resolve this problem by following these steps. Some times first step may resolve the issues and sometime you need to perform more than 1 steps

1) Clear the persistance directory

Stop all the opmn services


rm $INST_TOP/ora/10.1.3/j2ee/oacore/persistence/oacore_default_group_1/*
rm $INST_TOP/ora/10.1.3/j2ee/forms/persistence/forms_default_group_1/*
rm $INST_TOP/ora/10.1.3/j2ee/oafm/persistence/oafm_default_group_1/*


2) Change the timeout settings

The timeout value is defined in the $ORA_CONFIG_HOME/10.1.3/opmn/conf/opmn.xml file There are three entries to be concerned about, one for each of the managed OC4J containers (oacore, forms and oafm).

Default entry is

<start timeout=”600″ retry=”2″/>

Modifying the timeout value from “600” to “1800” may resolve the timeout error . You can only set it for entry “process-type id=”oacore””
or all entries giving timeout errors

changed to <start timeout=”1800″ retry=”2″/>

Steps would be
a) Stop all the opmn services


b) Take backup of the $ORA_CONFIG_HOME/10.1.3/opmn/conf/opmn.xml and change the timeout setting

c) $ADMIN_SCRIPTS_HOME/ startall


3) Run Autoconfig on the apps nodes

Steps would be
Stop all the opmn services


b) Run autoconfig

c) $ADMIN_SCRIPTS_HOME/ startall


4) Compile all the jsp files

a) Stop all the opmn services


b) cd $FND_TOP/patch/115/bin
./ –compile –flush -p 2
logfile set: /abc/oracle/TECH/inst/apps/TECH_LINUX/logs/appl/rgf/ojsp/ojspc_error.log
starting…(compiling all)
using 10i internal ojsp ver: 10
synchronizing dependency file:
enumerating jsps…8000
parsing jsp…8000
writing deplist…8000
initializing compilation:
eliminating children…5912 (-2088)
translating and compiling:
translating jsps…5912/5912 in 1m40s
compiling jsps…5912/5912 in 4m19s

c) $ADMIN_SCRIPTS_HOME/ startall





Leave a Reply