We have seen this error couple of times in the Concurrent manager Administer screen in our 11i/R12 EBS instances.
Below steps have proven helpful in sorting out this issue:
1. Stop all middle tier services including the concurrent managers.
Please make sure that no FNDLIBR, FNDSM, or any dead process is running.
2. Stop the database.
3. Start the database.
4. Go to cd $FND_TOP/bin
$ adrelink.sh force=y link_debug=y “fnd FNDLIBR”
$ adrelink.sh force=y link_debug=y “fnd FNDFS”
$ adrelink.sh force=y link_debug=y “fnd FNDCRM”
$ adrelink.sh force=y link_debug=y “fnd FNDSM”
5. Run the CMCLEAN.SQL script and commit..
6. Execute the following SQL:
select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where
CONCURRENT_QUEUE_NAME like ‘FNDSM%’;
7. Start the middle tier services including your concurrent manager.
References:
R12 E-Business Suite Concurrent Processing Managers Including OPP, Workflow Agent, and Workflow Listener Show Status “System Hold, Fix Manager before resetting counters” (Doc ID 2330129.1)
Manager Status Shows System Hold, Fix Manager before resetting counters (Doc ID 1507580.1)
- Oracle Multitenant DB 4 : Parameters/SGA/PGA management in CDB-PDB - July 18, 2020
- Details of running concurrent requests in Oracle EBS - May 26, 2020
- Oracle Multitenant DB 3 : Data Dictionary Architecture in CDB-PDB - March 20, 2020
Hi,
You have to provide MOS document, blindly we cannot do anything on Prod and other servers
You are right. I have added the MOS documents links now.