Concurrent Managers

Find Oracle Apps DBA scripts
Oracle Apps DBA Vishv Verma has published a nice summary of where the Oracle Apps DBA can find scripts to help with the concurrent manager. The concurrent manager is the job-scheduling component of Oracle Apps:

The following SQL scripts located under $FND_TOP/sql are useful when diagnosing concurrent manager problems:

1. afimchk.sql Tells the status of the ICM and PMON method

2. afcmstat.sql Lists active manager processes

3. afrqrun.sql Lists all the running, waiting and terminating requests

4. afrqwait.sql Lists requests that are constrained and waiting for the ICM to release them

5. afrqscm.sql Prints log file name of managers that can run a given request. It can be used to check for possible errors when a request stays in pending status. It requires a request id value.

6. afcmcreq.sql Prints the log file name of the manager that processed the request

7. afrqstat.sql Summary of completed concurrent requests grouped by completion status and execution type. It requires number of days prior to today on which to report parameter.

8. afimlock.sql Lists locks that the ICM is waiting to get

9. afcmrrq.sql Lists managers that currently are running a




In most organizations, it is common practice for an Oracle Apps DBA to check the Unix Process of the Internal Concurrent Manager using this command:
ps ?ef | grep CPMGR

or

ps ?ef | grep FNDCPMBR

applmgr 24988 24984  0   Dec 26 ?        5:16 FNDLIBR FND CPMGR FNDCPMBR sysmgr=""  sleep=30 logfile=/Ora_base/thor/rpt/co

applmgr 20050 20040  0   Dec 16 ?        3:30 FNDLIBR FND CPMGR FNDCPMBR sysmgr=""  sleep=30    logfile=/Ora_base/thor/rpt/co

applmgr 19900 19889  0   Dec 16 ?        4:53 FNDLIBR FND CPMGR FNDCPMBR sysmgr=""  sleep=30    logfile=/Ora_base/thor/rpt/co

applmgr 22629 22624  0   Dec 16 ?        0:56 FNDLIBR FND CPMGR FNDCPMBR sysmgr=""  sleep=30    logfile=/Ora_base/thor/applmg

applmgr 24757 24753  0   Dec 26 ?        5:04 FNDLIBR FND CPMGR FNDCPMBR sysmgr=""  sleep=30    logfile=/Ora_base/thor/rpt/co
However, either way the result will be the same because the search string exists in the output. If you have a single instance, then you would get just one output and that would indicate that the Internal Concurrent Manager Process is up (but not necessarily running or active). In case you have different releases of Oracle Apps on the same server and if the output of the command
Oracle Applications 11i eBusiness Suite DBA
Concurrent Managers

1. What is a Concurrent Manager ?

A Concurrent Manager is a background process which manages the concurrent requests in Oracle Apps 11i.

2. How many type of Concurrent Managers there are in Oracle Applications 11i ?
Internal Concurrent Manager (ICM): a background process which manages (start/ stop) the other managers. The ICM must run in order to start/ stop the other managers, so to process concurrent requests.
Standard Manager (SM): is the default concurrent manager. If a request is not defined to be run by a particular concurrent manager (Inventory Manager, Receivables Tax Manager, etc) the SM will take care of the concurrent request.
Conflict Resolution Manager (CRM): is handling any conflicts that might occur within the concurrent requests (for instance, 2 concurrent requests don't have to run in the same time on Monday between 1-2 Pm ). This task could be done by ICM as well.

3. How could I know if the ICM is started or not ?
A) Using the OAM:
Login to the E-Business Home Page -> System Administrator -> Concurrent : Manager/ Administer


Because 1 process is running that means the ICM is running. In this Form we can see if the other Concurrent Managers (CM) are running as well.
B) At the OS level (on UNIX)
ps -ef | grep FNDLIBR

ICM is not running:
[oracle@APPS VIS_apps]$ ps -ef | grep FNDLIBR
oracle 17846 7256 0 01:20 pts/2 00:00:00 grep FNDLIBR
[oracle@APPS VIS_apps]$
ICM is running:
[oracle@APPS VIS_apps]$ ps -ef | grep FNDLIBR
oracle 18069 18064 0 01:22 pts/2 00:00:00 FNDLIBR
oracle 18297 18137 0 01:22 ? 00:00:00 FNDLIBR
oracle 18298 18137 0 01:22 ? 00:00:00 FNDLIBR
oracle 18299 18137 0 01:22 ? 00:00:00 FNDLIBR
oracle 18303 18137 0 01:22 ? 00:00:00 FNDLIBR
oracle 18304 18137 0 01:22 ? 00:00:00 FNDLIBR
oracle 18623 7256 0 01:23 pts/2 00:00:00 grep FNDLIBR


4. How could I start/ stop the ICM ?

cd COMMON_TOP/admin/scripts/SID_localhost_name
[oracle@APPS VIS_apps]$ adcmctl.sh start apps/apps
or
[oracle@APPS VIS_apps]$ adcmctl.sh stop apps/apps


5. Where is the location of the ICM log file ?

If the environment variable APPLCSF is set, the ICM log file will be located in $APPLCSF/$APPLLOG. Otherwise, the ICM log will be located in $FND_TOP/$APPLLOG.
The log file name has the following format: SID_MMDD.mgr

The log file contains the following information:

========================================================================
Starting VIS_0401@VIS Internal Concurrent Manager -- shell process ID 18064

logfile=/APPS/viscomn/admin/log/VIS_apps/VIS_0401.mgr
PRINTER=noprint
mailto=oracle
restart=N
diag=N
sleep=60 (default)
pmon=20 (default)
quesiz=1 (default)
+---------------------------------------------------------------------------+
Application Object Library: Concurrent Processing version 11.5
Copyright (c) 1979, 199
....
..
Starting INVTMRPM Concurrent Manager : 01-APR-2008 01:22:36
Spawned Process 18135
Starting CRPINQMGR Concurrent Manager : 01-APR-2008 01:22:37
Starting PODAMGR Concurrent Manager : 01-APR-2008 01:22:37
Starting RCVOLTM Concurrent Manager : 01-APR-2008 01:22:37
Starting RCVOLTM14 Concurrent Manager : 01-APR-2008 01:22:37
Starting FNDCPOPP Concurrent Manager : 01-APR-2008 01:22:37
Starting XDP_Q_EVENT_SVC Concurrent Manager : 01-APR-2008 01:22:37
Starting XDP_APPL_SVC Concurrent Manager : 01-APR-2008 01:22:37
Starting WFALSNRSVC Concurrent Manager : 01-APR-2008 01:22:37
Starting WFMLRSVC Concurrent Manager : 01-APR-2008 01:22:38
Starting FNDCRM Concurrent Manager : 01-APR-2008 01:22:38
Starting STANDARD Concurrent Manager : 01-APR-2008 01:22:38
Starting STANDARD Concurrent Manager : 01-APR-2008 01:22:38
Starting STANDARD Concurrent Manager : 01-APR-2008 01:22:38
Starting PASMGR Concurrent Manager : 01-APR-2008 01:22:38
Starting XDP_MANAGER Concurrent Manager : 01-APR-2008 01:22:38
Starting OAMCOLMGR Concurrent Manager : 01-APR-2008 01:22:38
Starting INVMGR Concurrent Manager : 01-APR-2008 01:22:38
Starting MRPMGR Concurrent Manager : 01-APR-2008 01:22:38
Process monitor session ended : 01-APR-2008 01:22:38
Process monitor session started : 01-APR-2008 01:24:38
Spawned Process 18763
....



Disabling Concurrent Managers
Last update (2008-04-25 17:01:32)
 Date added (2008-02-18 13:07:55)
Summary
Sometimes you have to disable some Concurrent Managers. For example when you create a new single instance CLONE from a RAC E-Business Suite.

Of cource you can do it from the forms of the application, but if you want someting quick and dirty(for example to disable the SFM Concurrent Managers)

How to find if they are enabled
SELECT CONCURRENT_QUEUE_NAME, enabled_flag, node_name
FROM applsys.FND_CONCURRENT_QUEUES
WHERE CONCURRENT_QUEUE_NAME LIKE '%XDP%' AND enabled_flag = 'Y';

To disable one.
UPDATE applsys.FND_CONCURRENT_QUEUES SET enabled_flag = 'N'
WHERE CONCURRENT_QUEUE_NAME = 'XDP_SMIT_SVC';



Find concurrent manager nodes on Oracle Apps
1- Use the following query:
 sqlplus> select node_name from apps.fnd_nodes where support_cp='Y';

2- Check the variable TIER_NODE oa_var="s_isConc" YES  TIER_NODE on the context file:
$ grep s_isConc $CONTEXT_FILE
 YES means that this node is a concurrent manager node.

3- Check for the foundation library (FNDLIBR) processes
 $ ps -ef | grep FNDLIBR

4- Check the report server processes:
$ ps -ef | grep ora_rw