Monday, June 14, 2010

FNDOPP24553.txt:usdsop: exec failed during spawn/apps/local/TS10EF/inst/apps/TS10EF_'uname -n'/admin/scripts/java.sh: No such file or directory

Hi,
we had just cloned an R12.1.1 apps instance. In the target instance, TS10EF, the Output Post Processor and Workflow Background Listener managers were not coming up. The log of the OPP manager had the following error:
FNDOPP24553.txt:usdsop: exec failed during spawn/apps/local/TS10EF/inst/apps/TS10EF_'uname -n'/admin/scripts/java.sh: No such file or directory

Fix:
The issue is caused by incorrect AFJVAPRG environment variable setting. It should point to $ADMIN_SCRIPTS_HOME/java.sh. However, in our case, there was 'uname -n' in the environment variable which was causing this issue. To fix this, make the change in xml file for AFJVAPRG environment variable to reflect the context name (TS10EF_istg03) and run autoconfig. If you dont wish to run autoconfig, you can make the change in xml and also change AFJVAPRG the follow env file:
/apps/ts10ef/apps/apps_st/appl/istg03.env
Once the fix is done, log out , log in, source the env and start the concurrent managers. This should resolve the issue. However, in our case, it did not. In
the administer concurrent managers screen, we were seeing the following error:
"System Hold, Fix Manager before resetting counters "

To over come this issue, shutdown concurrent managers, run cmclean.sql (or basically set the process codes right) and start the managers. The problem would be fixed.

- Aravind Kamath Posral

No comments: