Standard manager fails to start

A concurrent program that had its basepath defined wrong when it was registered was submitted. which caused the standard manager to crash. and since the concurrent program was in the standard manager queue, the manager would crash as soon as the concurrent managers are restarted since the program is executed as soon as the concurrent managers are online. None of the log files reported any error except in the manager log of the deactivated processes ( of the standard manager) in the front end. all of the deactivated processes log's contained the request ID of the concurrent program.

The solution was to remove the concurrent program from the queue and correct the basepath of the concurrent program under the system administrator -> applications -> register to the correct custom top path as in the OS level and restart the concurrent managers.

oafm,forms and oacore not starting up after IP adress change

oafm, forms and oacore not starting up after IP adress change of the Oracle Applications Error from the logs:
adformsctl.sh: exiting with status 204
adoafmctl.sh: exiting with status 204
adoacorectl.sh: exiting with status 204

This is because the OC4J lock files contains the IP adress, after the ip adress change the lock files includes the wrong Ip adress which caused the OJ4J to fail.

To implement the solution perform the following steps:

1 - open a new shell and set your apps environment
2 - cd $ADMIN_SCRIPTS_HOME3 - adopmnctl.sh stop
4 - check if it is really down: ps -ef grep grep opm
5 - delete the following:

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/*

6 - adopmnctl.sh start
7 - check if the issue has been resolved: adapcctl.sh status