Troubleshooting Concurrent Managers

Lets today focus on Concurrent Manager & Issues related to concurrent Manager & how to fix them .

First of all you should be familiar with Concurrent manager concepts , if you wish to know more about CM check few links at my site

In above links you can find overview of CM, How to Start/Stop CM , parameters like CONCSUB, DISPLAY, SLEEP, PMON, QUESIZ …

At you can find basic overview of Troubleshooting Concurrent Manager

Lets classify how to start troubleshooting CM

Issues related to startup/shutdown of CM
If you try to start CM using or script & you encounter problem in starting CM then check for log files. All information related to why Concurrent Manager not coming up is recorder in log file at $APPLCSF/$APPLLOG with default name as $SID_$DD ( where DD is date on which you started Concurrent Manager ). This Concurrent Manager naming convention will be listed in file file (Concurrent Manager startup file). If $APPLCSF is not set then you can look for this file in $FND_TOP$APPLLOG

ICM is Up but some managers are still down
As you know script starts ICM (Internal Concurrent Manager) and its duty of ICM to start other Managers. If you see ICM is up with some other managers & Issue is with only Particular Managers then look for log files of these managers .

Concurrent -> Manager -> Administer -> Select manager which is not starting -> Click on “Processes” -> Click on “Manager Log” to find out error message.
These individual manager log file, you can access under $APPLCSF/$APPLLOG directory as well.

If you error message is not enough to find out cause of problem then you can enable debug on CM log files . You can enable diagnostics by changing DIAG_PARAM=”” to DIAG_PARAM=”Y” in (CM Startup script file)

Other things you can try for CM startup Issues :
Try to bounce CM & see all FNDLIBR processes are cleared before restrarting CM. You can run cmclean.sql command to clear any Invalid State against any request or manager. Check for any messages in log file. Check status of Manager from administer Concurrent Manager Window.
Concurrent -> Manager -> Administer (Login as System Administrator Responsibility)

More on CM Troubleshooting ..
Commonly faced issues in CM ..
Coming Soon

Raise any questions in Forum under Concurrent Manager Section

Share This Post with Your Friends over Social Media!

About the Author Atul Kumar

Oracle ACE, Author, Speaker and Founder of K21 Technologies & K21 Academy : Specialising in Design, Implement, and Trainings.

follow me on:

Leave a Comment:

Aashish says June 19, 2008

Nice Post on CM 🙂

nallavol says October 27, 2010

Hi Amit,

one concurrent program running for 3 hrs in clone node. but it is completing in 5 mi in production node..

please try to explain the steps to find out the problem..

i am new to oracle apps please try to explain in detail


nallavol says October 27, 2010

actually i tried to run
SQL>SELECT a.request_id, d.sid, d.serial# ,d.osuser,d.process , c.SPID
FROM apps.fnd_concurrent_requests a,
apps.fnd_concurrent_processes b,
v$process c,
v$session d
WHERE a.controlling_manager = b.concurrent_process_id
AND = b.oracle_process_id
AND b.session_id=d.audsid
AND a.request_id = &Request_ID
AND a.phase_code = ‘R’;

in my case concurrent request_id = 6250791.
while entering this it giving error :request id not identified like that……..
please try to tell me the solution for this

Atul Kumar says October 27, 2010

@ nallavol,
Replace &Request_ID with 6250791

@ praveen,

For slow running request check my post at


anil says December 15, 2011

After cloning (single to single) i got an issue icm status is active 1 and target is 0. By checkin g icm log file it shows as like log on denied.

Atul Kumar says December 17, 2011

@ Anil,
Post full error message, is this 11i or R12 ?

Did you run post clone on both apps tier and db tier ?

anil says December 17, 2011

its 11i,after cloning process DB is up and running and on applications side listener and tns is also good but my icm status is active:1 and target:0 by checking icm log file it shows as previously i told to you.
And on dbside i run exec fnd_conc_clone.setup_clean also

Akram says January 4, 2012

I problem with the concurrent manager after cloning. i run exec fnd_conc_clone.setup_clean
and it still not starting
the starting script does not give any error
but in applicaiton when I activate it, its status remain activating and does not start.
when I check manager log from concurrent processes form It give the following error:

An error occurred while attempting to establish an applicaiton file server connection with the node APPS. there may be a network configuration problem , or the TNS listener on the nodes APPS may not be runing …

please note the APPS is the name of the source machine before the cloning.

Atul Kumar says January 4, 2012

@ Akram,
After running setup_clean did you run autoconfig to register nodes (check FND_NODES table in apps schema)?

Your issue seems because apps listener is down. Ensure that all services (including apps listener) on middle tier is running .

Akram says January 5, 2012

the fnd_nodes tabel has two rows
LEASE1 (the current host name)

I am getting an eror when I run adautocfg.cmd

AutoConfig could not successfully execute the following scripts: Directory: F:\oracleqatar\qtarcomn\admin\install\QTAR_lease1
afcpctx.cmd INSTE8_PRF 3

Atul Kumar says January 5, 2012

@ Akram, search for afcpctx in metalink (My Oracle Support) and you will see 6-7 hits.

Reply says June 12, 2013

Hi Atul,

I have one Oracle EBS 11i system,

Setup is like this

DB Tier node (Single instance 32 bit Oracle)
Web+Concurrent mgr node on separate Virtual machine.

Often one of the MRP concurrent manager gets memory error as following. Is it linked with memory usage on DB Tier or on the Concurrent manager node? How to troubleshoot them?

Errors reported on log file:

APP-MRP-22086: mrlgpd_gen_pl_ord_dem: Cannot allocate memory for op_seq_num_list

Cause: The current routine cannot allocate memory for the specified entity.

Action: Contact your customer support representative.

Total memory usage: 1390708

***** End Of Program – Memory-Based Planner *****



Add Your Reply