Oracle Application Server Shutdown ProblemOracle Application Server Shutdown Problem
You will have problem in Oracle Application Server processes if the process was not shutdown gracefully.
This often happens when physical server restarted without a clean shutdown on the Oracle Application Server.
Oracle Application Server Shutdown Problem
$ $ORACLE_HOME/opmn/bin/opmnctl status Processes in Instance: oracle.application.server.com -------------------+--------------------+---------+--------- ias-component | process-type | pid | status -------------------+--------------------+---------+--------- LogLoader | logloaderd | N/A | Down dcm-daemon | dcm-daemon | N/A | Down WebCache | WebCache | N/A | Down WebCache | WebCacheAdmin | N/A | Down OC4J | home | 4646 | Stop OC4J | OC4J_BI_Forms | N/A | Down HTTP_Server | HTTP_Server | N/A | Down Discovererverer | ServicesStatus | N/A | Down Discovererverer | PreferenceServer | N/A | Down DSA | DSA | N/A | Down
$ $ORACLE_HOME/opmn/bin/opmnctl stopall opmnctl: stopping opmn and all managed processes... ================================================================================ opmn id=g4u0962:6200 0 of 1 processes stopped. ias-instance id=oracle.application.server.com ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ias-component/process-type/process-set: OC4J/home/default_island Error --> Process (pid=4646) time out while waiting for a managed process to stop Log: /Discoverer/oracle/opmn/logs/OC4J~home~default_island~1 opmnctl: graceful stop of processes failed, trying forceful shutdown...
So check on the PID 4646, it seems that the Unix PID process doesn’t belongs to the Oracle Application Server.
Oracle Application Server Shutdown Solution
To correct and resolve this issue in Oracle Application Server, please follow the steps as below: -
$ $ORACLE_HOME/opmn/bin/opmnctl shutdown opmnctl: opmn is not running $ cd $ORACLE_HOME/opmn/logs $ mkdir oracle_backup $ mv *.* oracle_backup $ $ORACLE_HOME/opmn/bin/opmnctl start opmnctl: opmn started $ $ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=OC4J opmnctl: starting opmn managed processes... $ $ORACLE_HOME/opmn/bin/opmnctl status Processes in Instance: oracle.application.server.com -------------------+--------------------+---------+--------- ias-component | process-type | pid | status -------------------+--------------------+---------+--------- LogLoader | logloaderd | N/A | Down dcm-daemon | dcm-daemon | N/A | Down WebCache | WebCache | N/A | Down WebCache | WebCacheAdmin | N/A | Down OC4J | home | 27011 | Alive OC4J | OC4J_BI_Forms | 27012 | Alive HTTP_Server | HTTP_Server | N/A | Down Discovererverer | ServicesStatus | N/A | Down Discovererverer | PreferenceServer | N/A | Down DSA | DSA | N/A | Down
As you see, the logs was moved away and the Oracle Application Server OC4J processes can be started without any problem.
Now the OC4J process was managed to be started up in the Oracle Application Server using the new Unix PID.
Leave a Comment
Recent Comments