adoacorectl.sh adformsctl.sh adoafmctl.sh exiting with status 150 or unable to start oacore oc4j in r12

To fix this error adoacorectl.sh exiting with status 150 we have to follow the below steps.

cat $LOG_HOME/ora/10.1.3/opmn/opmn.log

18/09/29 11:41:21 [libopmnoc4j] OC4J ping attempt timed out
18/09/29 11:41:21 [libopmnoc4j] Process Ping Failed: default_group~oacore~default_group~1 (1726679358:1966)
18/09/29 11:42:11 [libopmnoc4j] OC4J ping attempt timed out
18/09/29 11:42:11 [libopmnoc4j] Process Ping Failed: default_group~oacore~default_group~1 (1726679358:1966)
18/09/29 11:42:11 [libopmnoc4j] Process Unreachable: default_group~oacore~default_group~1 (1726679358:1966)
18/09/29 11:42:11 [pm-process] Restarting Process: default_group~oacore~default_group~1 (1726679358:1966)
18/09/29 11:43:25 [pm-process] Starting Process: default_group~oacore~default_group~1 (1726679358:0)
18/09/29 11:43:32 [pm-process] Process Alive: default_group~oacore~default_group~1 (1726679358:37890)
18/09/29 11:43:39 [pm-requests] Request 58d Started.  Command: /start?process-type=oacore
18/09/29 11:43:39 [pm-requests] Request 58d Completed. Command: /start?process-type=oacore

You may face error as following.

adformsctl.sh exiting with status 150

adoafmctl.sh exiting with status 150

adoacorectl.sh exiting with status 150

Go to $INST_TOP/ora/10.1.3/j2ee/oacore/persistence/oacore_default_group_1 on application tier and look for jms.state and *.lock files.

drwxr-xr-x 3 applmgr dba 4096 Jan  2  2017 persistence
-rw-r–r– 1 applmgr dba  108 Sep 29 11:43 scheduler_notifications.lock
-rw-r–r– 1 applmgr dba  512 Sep 29 11:43 scheduler_notifications
-rw-r–r– 1 applmgr dba  512 Sep 29 11:43 Oc4jJmsExceptionQueue
-rw-r–r– 1 applmgr dba  108 Sep 29 11:43 scheduler_jobstore.lock
-rw-r–r– 1 applmgr dba  512 Sep 29 11:43 scheduler_jobstore
-rw-r–r– 1 applmgr dba  108 Sep 29 11:43 scheduler_events.lock
-rw-r–r– 1 applmgr dba  512 Sep 29 11:43 scheduler_events
-rw-r–r– 1 applmgr dba 4096 Sep 29 11:43 jms.state

If you find them in this location once all your services are stop. Delete or rename them. Once you are done try again. Now OACORE OC4J service will come up.

Solution:

1. Stop application services 

To stop application services, you may click here and check below section

1.    Stop the Middle Tier Services.

2. Clear contents of the persistence directory

rm -rf $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/persistence/*
rm -rf $ORA_CONFIG_HOME/10.1.3/j2ee/oafm/persistence/*
rm -rf $ORA_CONFIG_HOME/10.1.3/j2ee/forms/persistence/*

3. Start application services

To restart the application services, you check below section to click here.

4.    Restart Application (Middle Tier) services