Concurrent Managers Fail to Start, Verify that findev has been registered for concurrent processing
After migration of the Applications tier the concurrent managers do not start. Only a single FNDLIBR process is seen and the following errors are seen in the log file:
Process monitor session started : 04-DEC-2007 12:01:49
Could not contact Service Manager FNDSM_DHSRVMDS518_SDBA. The TNS alias could not be located, the listener process on DHSRVMDS518 could not be contacted, or the listener failed to spawn the Service Manager process.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 04-DEC-2007 12:06:02
Starting STANDARD Concurrent Manager : 04-DEC-2007 12:06:02
Could not initialize the Service Manager FNDSM_DHSRVMDS519_SDBA. Verify that DHSRVMDS519 has been registered for concurrent processing.
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /u02/app/oracle/sdbaappl/fnd/11.5.0/bin/FNDLIBR.
The issue was caused by incorrect node names in the FND_NODES table, the table had not been updated to remove non existent nodes.
1 Run AutoConfig on the database tier.
2. Execute FND_CONC_CLONE.SETUP_CLEAN
3 Run AutoConfig on the apps tier
4. Check if AutoConfig completed successfully.
5. Verify the managers not start
Shutdown Concurrent Managers and update the FND table:
1. Go to the $OAD_TOP/admin/scripts
2. adcmctl.sh apps/
3. Connect to SQL*PLUS apps/
4. SQL > select target_node from FND_CONCURRENT_QUEUES;
This may return the name of an old machine
5. SQL > update FND_CONCURRENT_QUEUES
6. SQL > commit;
7. SQL > exit
8. adcmctl.sh apps/apps start
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/46907/viewspace-217011/，如需转载，请注明出处，否则将追究法律责任。