adopmnctl.sh: exiting with status 206

Hi,

Of late, I faced an issue while starting up the oacore component in our R12 environment. There were no errors logged in any of the log files except the error status code of 206 returned by opmnctl.sh .

ias-component/process-type/process-set:
OC4J/oacore/default_group/

Error
--> Process (index=1,uid=32979870,pid=13697)
failed to start a managed process after the maximum retry limit
Log:
/apps/local/INSTANCE_NAME/inst/apps/INSTANCE_NAME_SERVER_NAME/logs/ora/10.1.3/opmn/OC4J~oacore~default_group~1

ias-component/process-type/process-set:
OC4J/oafm/default_group/

Error
--> Process (index=1,uid=32979871,pid=13716)
failed to start a managed process after the maximum retry limit
Log:
/apps/local/INSTANCE_NAME/inst/apps/instance_name_server_name/logs/ora/10.1.3/opmn/OC4J~oafm~default_group~1


03/31/09-07:12:49 :: adopmnctl.sh: exiting with status 206



FIX:

- cd $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/persistence/
- rm -rf *
- repeat the above step for oafm. The path will be cd $ORA_CONFIG_HOME/10.1.3/j2ee/oafm/persistence/

Troubleshooting Tips:

- use any command like lsof to see what files are being accessed to get an idea.

On the side lines, if you navigate to $IAS_ORACLE_HOME/opmn/bin and try to use opmnctl to check status or to set log levels, you will see an issue that says unable to read the opmn.xml file. For this, you need to set the $ORACLE_CONFIG_HOME to point to 10.1.3 instead of 10.1.2.

- Aravind Kamath