R12: Time Out on Stop Action for OC4J and Log Reports "Error: Password unavailable for OPMN flag on" (Doc ID 974386.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Applications Technology Stack - Version 12.0 to 12.0.6 [Release 12.0]
Information in this document applies to any platform.

Symptoms

Starting the OC4J processes (oacore, forms, oafm) for E-Business Suite R12.0 or R12. 1 is successful and the  command $INST_TOP/admin/scripts/adapcctl.sh status reports all processes are up and running similar to:

Checking status of OPMN managed FORMS OC4J instance ...
Processes in Instance: VIS_<xxxx>
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
OC4JGroup:default_group          | OC4J:oafm          |   23110 | Alive
OC4JGroup:default_group          | OC4J:forms         |   17561 | Alive
OC4JGroup:default_group          | OC4J:oacore        |   23108 | Alive
HTTP_Server                      | HTTP_Server        |   23107 | Alive
adformsctl.sh: exiting with status 0

 

However when running the command to stop one or more of the OC4J (*) processes it takes about 2 minutes before script ends with the following:

You are running adoacorectl.sh version 120.13
Stopping OPMN managed OACORE OC4J instance ...
adoacorectl.sh: exiting with status 204
adoacorectl.sh: check the logfile .../VIS/inst/apps/<SID_server>/logs/appl/admin/log/adoacorectl.txt for more information ...

(*) The example shows results of the oacore OC4J. However exactly the same applies to the  forms and oafm OC4J when using their respective scripts.
 
The adoacorectl.txt reports the following:
================================================================================
12/07/09-13:32:44 :: adoacorectl.sh version 120.13
12/07/09-13:32:44 :: adoacorectl.sh: Stopping OPMN managed OACORE OC4J instance
opmnctl: stopping opmn managed processes...
================================================================================
opmn id=<server.domain>:6200
    0 of 1 processes stopped.
ias-instance id=<SID_server_server.domain>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
--------------------------------------------------------------------------------
ias-component/process-type/process-set:
    default_group/oacore/default_group/
Error
--> Process (index=1,uid=700593153,pid=23108)
    time out while waiting for a managed process to stop
    Log:
    .../inst/apps/<SID_server>/logs/ora/10.1.3/opmn/default_group~oacore~default_group~1.log
12/07/09-13:34:46 :: adoacorectl.sh: exiting with status 204
 
In the LOG_HOME/ora/10.1.3/opmn/default_group~oacore~default_group~1.log the following is reported
--------
09/12/07 13:32:44 Stop process
--------
Error: Password unavailable for OPMN flag on
 
Note: The result is still that the OC4J process is terminated. This however is the result of kill performed on the PID after the time-out, rather then the OC4J process closing down properly after 'stop' notification.

Changes

In the reported case it appeared to be related to (preparation of) upgrade to newer AS10G release. 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms