Oacore Service Hanging at Startup in Oracle EBS R12.1.3


Before
=====
$ adopmnctl.sh status


You are running adopmnctl.sh version 120.6.12010000.5


Checking status of OPMN managed processes…
Processes in Instance: ebstest_apptest.apptest.user.com
———————————+——————–+———+———
ias-component | process-type | pid | status
———————————+——————–+———+———
OC4JGroup:default_group | OC4J:oafm | 8015 | Init
OC4JGroup:default_group | OC4J:forms | 7171 | Alive
OC4JGroup:default_group | OC4J:oacore | 3276 | Init
HTTP_Server | HTTP_Server | 2942 | Alive


Casue: This issue may occur after an OS crash, reboot or services restart.
If file $COMMON_TOP/cacheLock file exists before oacore service is started, the above thread will be locked and the oacore service will hang until timed out.


Solution:
Remove $COMMON_TOP/cacheLock file which is a 0 bytes file created at startup time.


1)stop application services make sure no process are running.
2)go to common top


cd $COMMON_TOP
$ mv cacheLock cacheLock_bkp


3)started the application services and when I checked the status,it was started successfully and no more issues.Below are the details.


$ adopmnctl.sh status


You are running adopmnctl.sh version 120.6.12010000.5


Checking status of OPMN managed processes…


Processes in Instance: ebstest_apptest.apptest.user.com
———————————+——————–+———+———
ias-component | process-type | pid | status
———————————+——————–+———+———
OC4JGroup:default_group | OC4J:oafm | 27257 | Alive
OC4JGroup:default_group | OC4J:forms | 26249 | Alive
OC4JGroup:default_group | OC4J:oacore | 24769 | Alive
HTTP_Server | HTTP_Server | 24447 | Alive
  • January 11, 2018 | 31 views
  • Comments