JUST RELAX DBA

Adoafmctl.sh Failed To Start Managed Process After The Maximum Retry

Limit.

Most of the DBA's faced this error while starting Adoafmctl.sh failed once after clone or existing
instance. There are many reasons for failing services. Here we are going to cover a few of the
scenarios that most commonly faced by the DBA's.

Scenario 1:
Adoafmctl.sh failed to start a managed process after the maximum retry limit
In version 12.1.3, IAS for Applications Technology when attempting to start oafm with
$ADMIN_SCRIPTS_HOME/adoafmctl.sh start,
The following error occurs. The issue has the resulting business impact; Due to this issue, users
cannot start OAFM service successfully.

11/09/19-05:23:11: adoafmctl.sh: Starting OPMN managed OAFM OC4J instance

opmnctl: starting opmn managed processes...

================================================================================

opmn id=xxxxxx.xxxxx.com:xxxx

0 of 1 processes started.

ias-instance id=PROD_xxxxx.xxxxx.xxxxx.com

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

--------------------------------------------------------------------------------

ias-component/process-type/process-set:

default_group/oafm/default_group/

Error

--> Process (index=1,uid=189695577,pid=36855)

failed to start a managed process after the maximum retry limit

Gokulkumar Page 1
JUST RELAX DBA

Log:

/doyen/inst/apps/TEST_xxxxx/logs/ora/10.1.3/opmn/default_group~oafm~default_group~1.log

11/09/19-05:24:46 :: adoafmctl.sh: exiting with status 204

=================================================================================

After checking $LOG_HOME/ora/10.1.3/opmn/oafm_default_group_1/, and found below error

message:

FileName = oafmstd.out

11/09/19 05:23:01 Oracle Containers for J2EE 10g (10.1.3.5.0) initialized

11/09/19 05:23:04 Shutting down...

11/09/19 05:23:24 INFO: SecuritySensitive.lookupException Malformatted credentials for user

ASADMIN. Please check your JAZN repository.; password is not available for indirect password via
application context (user: oc4jkeystoreadmin)

11/09/19 05:23:36 Fatal error: server exiting

11/09/19 05:23:39 INFO: SecuritySensitive.lookupException Malformatted credentials for user

ASADMIN. Please check your JAZN repository.; password is not available for indirect password via
application context (user: oc4jkeystoreadmin)

11/09/19 05:23:49 Fatal error: server exiting

11/09/19 05:24:05 INFO: SecuritySensitive.lookupException Malformatted credentials for user

ASADMIN. Please check your JAZN repository.; password is not available for indirect password via
application context (user: oc4jkeystoreadmin)

11/09/19 05:24:45 Fatal error: server exiting

FileName = oafmstd.out

Gokulkumar Page 2
JUST RELAX DBA

11/09/19 05:23:01 Oracle Containers for J2EE 10g (10.1.3.5.0) initialized

11/09/19 05:23:04 Shutting down...
11/09/19 05:23:24 INFO: SecuritySensitive.lookupException Malformatted credentials for user
ASADMIN. Please check your JAZN repository.; password is not available for indirect password via
application context (user: oc4jkeystoreadmin)
11/09/19 05:23:36 Fatal error: server exiting
11/09/19 05:23:39 INFO: SecuritySensitive.lookupException Malformatted credentials for user
ASADMIN. Please check your JAZN repository.; password is not available for indirect password via
application context (user: oc4jkeystoreadmin)
11/09/19 05:23:49 Fatal error: server exiting
11/09/19 05:24:05 INFO: SecuritySensitive.lookupException Malformatted credentials for user
ASADMIN. Please check your JAZN repository.; password is not available for indirect password via
application context (user: oc4jkeystoreadmin)
11/09/19 05:24:45 Fatal error: server exiting

Cause:

The issue is caused by missing exclamation mark (!) of user ASADMIN.

Issue can be checked with
$ORA_CONFIG_HOME/10.1.3/j2ee/oafm/config/system-jazn-data.xml

<user>
<name>ASADMIN</name>
<display-name>Default Apps SOA User</display-name>
<description>Used by SOAProvider for DB connection</description>
<credentials>asadmin</credentials>
</user>

Solution:

First take backup of $ORA_CONFIG_HOME/10.1.3/j2ee/oafm/config/system-jazn-data.xml and then

manually edit the system-jazn-data.xml file and change the following section for the ASADMIN user:

FROM:
<user>
<name>ASADMIN</name>
<display-name>Default Apps SOA User</display-name>
<description>Used by SOAProvider for DB connection</description>
<credentials>asadmin</credentials>
</user>

TO:

Gokulkumar Page 3
JUST RELAX DBA

<user>
<name>ASADMIN</name>
<display-name>Default Apps SOA User</display-name>
<description>Used by SOAProvider for DB connection</description>
<credentials>!asadmin</credentials>
</user>

NOTE: The change is adding the exclamation mark (!) "!" before the password.

Then try starting OAFM and check results the OAFM services will be up and running.

Best Practices:

1. It is mandatory to change ADADMIN password for only those using SOA in their environment, reset of
them does not requested to change the password.

2. Leave a comment line in the file that insists to add exclamation mark (!) "!" before the password.

Scenario 2:

While starting OPMNCTL services OC4J:oafm services was not starting up, it will be in the status "Init"
for some time after timeout it will failed.

The following error occurs. The issue has the following business impact, Due to this issue, users cannot
start OAFM service successfully.

Processes in Instance: TEST_doyen.doyen.doyensys.com

---------------------------------+--------------------+---------+----------+------------+----------+-----------+---------------

ias-component | process-type | pid | status | uid | memused | uptime | ports

---------------------------------+--------------------+---------+----------+------------+----------+-----------+----------------

OC4JGroup:default_group | OC4J:oafm | 88312 | Init | 1039750491 | 544712 | 0:05:21

| N/A

OC4JGroup:default_group | OC4J:forms | 77453 | Alive | 1039750490 | 620404 | 0:05:45

| rmi:20505,jms:23505,ajp:22005

OC4JGroup:default_group | OC4J:oacore | 36770 | Alive | 1039750489 | 433284 |

0:09:02 | rmi:20006,jms:23006,ajp:21506

Gokulkumar Page 4
JUST RELAX DBA

OC4JGroup:default_group | OC4J:oacore | 16774 | Alive | 1039750488 | 157468 |

0:09:02 | rmi:20005,jms:23005,ajp:21505

HTTP_Server | HTTP_Server | 86727 | Alive | 1039750487 | 832264 | 0:05:43 |

https1:3333,http1:8003

After some time OC4J:oafm will be down.

Processes in Instance: SID_machine.machine.domain

-------------------+--------------------+---------+----------------------
ias-component | process-type | pid | status
-------------------+--------------------+---------+-----------------------
OC4JGroup:default_group | OC4J:oafm | N/A | Down

Log:
$INST_TOP/apps/SID_machine/logs/ora/10.1.3/opmn/default_group~oafm~default_group~1

Error
--> Process (index=1,uid=349189076,pid=15039)
time out while waiting for a managed process to start
12/09/19-06:13:11 :: adoafmctl.sh: exiting with status 152

Cause:

Existing JSP Tag Library Cache content was preventing the TLD Cache for the map viewer app from
initializing correctly.

Solution:

To implement the solution test the following steps:

1. Clear the TLD cache:

2. Stop all middle tier services.

3. Delete/backup the file:

$COMMON_TOP/_TldCache

4. Start OPMNCTL services and re-test.

Gokulkumar Page 5
JUST RELAX DBA

The above steps will fix the issue, in some case once after clearing cache file to problem still exits.
For those environment we have follow the below steps to fix the issue.

1. Stopped all the application services.

2. Cleared persistence cache.

rm -fr $INST_TOP/ora/10.1.3/j2ee/oacore/persistence/*
rm -fr $INST_TOP/ora/10.1.3/j2ee/oafm/persistence/*
rm -fr $INST_TOP/ora/10.1.3/j2ee/forms/persistence/*
3. Run autoconfig.
4. Start the application services

Best Practices:
1. Shutdown all the services completely, kill all died pid and defunct session before starting the
services.
2. Clear persistence.

Reference:
Adoafmctl.sh Failed To Start A Managed Process After The ....
https://support.oracle.com/knowledge/Oracle%20E-Business%20Suite/1599784_1.html

Gokulkumar Page 6