This post covers an Overview of Concurrent Manager, one of the most common tasks that Oracle Apps DBA‘s (apart from Patching, Cloning & Troubleshooting).
If you are new to Oracle AppsDBA or already working as Apps DBA but on version 11i or R12.1 then I highly recommend you first to go through Architecture, Installation, Start/Stop, File System, and Patching in Oracle AppsDBA R 12.2 for AppsDBAs here (FREE lessons from our Oracle Apps DBA Training)
1. Concurrent Manager
Concurrent Manager service is a batch processing tool which provides scheduling and queuing functionality for background jobs and is used by most of the Oracle Applications modules. It is a key service within Ebusiness Suite which runs the user requests in the background thus ensuring that the user can continue with other days to day tasks while the requested change/activity is carried out by the Concurrent Manager.
2. Variables/Executables for CM
- $APPLCSF is the top-level directory in which the Concurrent Manager puts log and output files.
- $APPLLOG & $APPLOUT are the subdirectories in which the Concurrent Manager puts log and output files.
- $APPLTMP is the directory in which Oracle Applications temporary files are created.
- $APPLPTMP is the directory in which PL/SQL output files are created.
Note: The value must be exactly same as “utl_file_dir” value in init.ora parameter file.
- FNDLIBR ( executable ) The ICM (Internal Concurrent Manager) spawns FNDLIBR processes based on the concurrent manager definitions. The number of FNDLIBR processes at the operating system level will be equal to the total number of max requests for each concurrent manager defined plus one for the ICM.
FNDLIBR processes can be queried up at the operating system level by using
$ ps -ef | grep FNDLIBR
[applmgr@1705ecloud05 scripts]$ ps -ef | grep FNDLIBR
applmgr 5075 5069 0 04:54 ? 00:00:01 FNDLIBR
applmgr 12919 12169 0 06:33 pts/9 00:00:00 grep FNDLIBR
Remember there are also other manager processes for INVLIBR, MFGLIBR, etc.
3. Start/Stop & Check Concurrent Managers (CM)
Prior to startup of CM service, you must run the environment file APPS<CONTEXT_NAME>.env
The default filename for the environment file in R12.2 is EBSapps.env and set the environment to Run Edition.
a) Start Concurrent Manager (CM) in R12:
b) Stop Concurrent Manager in R12
c) To check Status of Concurrent Manager
You are running adcmctl.sh version 120.19.12020000.7
Internal Concurrent Manager is Active.
adcmctl.sh: exiting with status 0
adcmctl.sh: check the logfile /u01/oracle/PRD122/fs1/inst/apps/PRD12111_1705ecloud05/logs/appl/admin/log/adcmctl.txt for more information …
Note: Script to start/stop concurrent manager, Similar to one in 11i. (This script, in turn, calls startmgr.sh )
4. Concurrent Manager Log file location in R12:
Each concurrent request (run by Concurrent Manager) generates a log file for details regarding the request and an outfile for report details. There are 3 types of log files for concurrent processing:
A) Request Log File – documents the execution of a particular request ( l.req )
B) Manager Log File – documents the performance of a concurrent manager process. ( W.mgr )
C) Internal Manager Log File – documents the performance of the ICM.( ). This log file displays the parameters used with the’adcmctl’ command.
- Log files can be viewed as an operating system level of $product_TOP/$APPLLOG or $APPLCSF/$APPLLOG.
- $APPLLOG is always set and $APPLCSF is optional. Log files can also be viewed from within the applications from the View Concurrent Requests Form
The out files contain the output generated from a concurrent processing report. Out files can be viewed at an operating system level of $product_TOP/$APPLOUT or $APPLCSF/$APPLOUT (if set). Out files can also be viewed from within the applications from View Concurrent Requests form ( \ Nav Con Req).
5. Concurrent Managers Tables in R12
- FND_CONCURRENT_PROCESSES FND_CONCURRENT_REQUESTS
FND_CONCURRENT_PROCESSES — Lists information about managers; Useful for determining UNIX and Oracle process is associated with managers; Identifies logfiles associated with managers.
FND_CONCURRENT_REQUESTS — Primary jobs submission table; Queried by the managers; Jobs are inserted into this table; Table can grow rather large thus affecting performance; Cleanup scripts available with the Applications.
FND_CONCURRENT_PROGRAMS –Stores information about concurrent programs. Each row includes a name and description of the concurrent program. Each row also includes the execution methods for the program (EXECUTION_METHOD_CODE), the argument method (ARGUMENT_METHOD_CODE), and whether the program is constrained (QUEUE_METHOD_CODE).
Did you get a chance to download 6 Concurrent Manager CM Must Read Docs For Oracle Apps DBAs EBS R12? If not, then get it now by clicking on the link below.
Are you having any queries or hitting any issues in R12.2 Concurrent Manager (CM)?
Stay tuned for Performance Tuning & How to Troubleshoot Long running Concurrent Request in EBS R12