How to find Concurrent Manager Node in Multi-Node environment ?
Method 1: SQLPLUS> select node_name from apps.fnd_nodes where support_cp='Y';
Method 2: Execute "ps -ef grep FNDLIBR" under application User on all nodes where FND (Foundation) LIBR (Library) is executable.
Can I delete a concurrent manager?
No. You can only disable/Enable the manager by checking the 'Enabled' checkbox
How do I enable/disable the Conflict Resolution Manager?
Use the system profile option 'Concurrent: Use ICM'. Setting this to 'No' (which is the default) allows the CRM to be started. Setting it to 'Yes' causes the CRM to be shutdown and the Internal Manager (ICM) will take over the conflict resolution duties. If the CRM will not start (it is started automatically by the ICM), check this profile option. Note that using the ICM to resolve conflicts is not recommended. The CRM's sole purpose is to resolve conflicts, while the ICM has other functions to perform as well. Only set this option to 'YES' if you have a good reason to do so.
How do I clean out the Concurrent Manager tables?
Run the script, cmclean.sql, article Note 134007.1
How do we process more concurrent requests concurrently?
Login as a Sysdba and navigate ->Concurrent -> Manager -> Define and Query for the relevant concurrent manager), done in two steps: (i) Increase the Number of Target processes for the manager (ii) Change the cache size of the concurrent manager.
How to Handle hang Concurrent Request or How to Kill Concurrent Request session ?
Step 1 Mapping Concurrent request Id to Sid and serai# by using following query
select v.request_id, s.sid,s.serial#,s.event,p.spidfrom apps.fnd_conc_requests_form_v v,v$process p,v$session swhere v.request_id = ‘'and v.oracle_process_id = p.spid(+)and p.addr = s.paddr(+)
Step 2 Execute following command and supply output from query 1
SQL> alter system kill session 'sid, serial#'
