Resolving Concurrent Manager Issues in R12

Concurrent Managers did not start properly

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 $FND_TOP/bin and run below

$ 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 following queries connect with apps user.

$ sqlplus apps/
SQL> @ CMCLEAN.SQL (download script from note 134007.1) 
SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;
SQL> commit;

6. Execute the following SQL to Verify the Concurrent Manager definition

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.

8. Retest the issue. 


Difference between fnd_conc_clone.setup_clean and cmclean.sql

fnd_conc_clone.setup_clean

fnd_conc_clone is a package own by apps schema. This procedure cleanup fnd_nodes table in the target to clear source node information as part of cloning. When we execute fnd_conc_clone.setup_clean it deletes the information from the below tables.

fnd_concurrent_queue_size
fnd_concurrent_queues_tl
fnd_concurrent_queues
fnd_nodes;

Steps to proceed

sqlplus apps/
SQL> exec fnd_conc_clone.setup_clean;
SQL> commit;

cmclean.sql

If we stop conc manager using abort options then concurrent requests will be in running state ,Next when we start concurrent manager the processes will not start properly.
To cleanup running and pending requests we use cmclean.sql this script will update the below tables.

fnd_concurrent_processes
fnd_concurrent_queues
fnd_concurrent_requests
fnd_conflicts_domain
fnd_concurrent_conflict_sets

Note: cmclean.sql and fnd_conc_clone.setup_clean touch different set of concurrent request tables. Its better to run both during the clone. 

Related Oracle Notes

Concurrent Processing - Concurrent Manager Recovery Troubleshooting Wizard (Doc ID 134007.1)

Concurrent Processing - After Cloning all the Concurrent Managers do not start for the cloned Instance (Doc ID 555081.1)

Concurrent Processing - R12 Output Post Processor Service Not Coming Up. (Doc ID 460578.1)

After Clone Concurrent Manager Will Not Come Up and Columns in fnd_concurrent_queues Table are Not Getting Updated With Node Names (Doc ID 1646026.1)

Concurrent Processing - Output Post Processor is Down with Actual Process is 0 And Target Process is 1 (Doc ID 858813.1)