Concurrent Manager Performance tuning R12.2
Concurrent manager process flow
FNDSM is initiate the concurrent manager in OS
processer.
Then start the database session and read the settings.
Update the fnd_concurrent_processes and
fnd_concurrent_queues tables
Build SQL for quiring the request queue.
Execute the sql to request concurrent manager.
Checking for Sleep time seconds, Pending requests
Checking the “Cache size” number of requests into the
execution cache.
Execute the request from the execution Queue.
Update the status code of the concurrent request.
Execute the request and update the status code.
If Concurrent Managers are not
starting
Check Concurrent Manager log
files Click here
Check the database alert log for
any space issue.
Check the application tier
filesystem and Middle tier file system space and /tmp directory space.
Check application listner Running/Not
adalnctl.sh status
Run the adcmctl script with debug option will get some idea where its failed
sh -x adcmctl status apps/appspw
Check if FNDSM service is Running/Not
$APPLCSF/$APPLLOG/FNDSM*.log
ps -ef | grep FNDSM
Check tnsping to FNDSM TNS entry
tnsping
FNDSM_<hostname>_<SID>
If required please run the
cmclean.sql and bounce the concurrent manager
Concurrent
manager sanity checks
Submit “Active User” concurrent request and check if
it’s completed.
If concurrent program fails, check the clog files
Check the log and output file if not able to login
check Apps listener is running/not.
Check Internal concurrent manager and standard manager
running front end.
Check UNIX process for backend “Ps-ef |grep FNDLIBR”
If manager is failing due to some issue check the database lock.
Tuning
the concurrent Queues.
Sleep
seconds:
Is the number of seconds your concurrent manager waits
between checking the list of pending concurrent requests.
Example:
If sleep second value is 2 Minutes then CM will check
pending concurrent requests every 2-min
For peak time we can increases the sleep seconds.
Cache size:
Cache size means the number of requests cached and
cache size value should be the twice of the number of the target process.
Example:
If manager work shift has 1 target process and cache value of 3. Then it will read the 3 requests and try to run those 3 requests before reading any new requests.
Process:
Increase If it pending/normal request high.
Example:
If Standard manager high number of pending request in
the queue then we can increase the process.
We need to always keep monitoring below tables
FND_CONCURRENT_REQUESTS
FND_CONCURRENT_PROCESSES
FND_CRM_HISTORY
FND_ENV_CONTEXT
FND_TEMP_FILES
Above tables should be Defragment periodically
We need to collect gather stats for above tables.
Check the CM from OS Level
ps –ef |grep FNDLIBR
ps –ef |grep FNDCRM
ps –ef |grep INVLIBR
Concurrent
Manager Related Profiles
Applications
Servlet Agent
Applications
Web Agent
Concurrent
: Active Request Limit
Concurrent
: Conflicts Domain
Concurrent
: PMON method
Concurrent
: Report Access Level
Concurrent:
Sequential Requests
RRA:
Maximum Transfer Size
RRA: Delete
Temporary Files
Cleaning the CM Tables
CMCLEAN.sql
This script
re-sets the flags for requests to completed to allow the
Managers to
come up. No longer supported and MUST not be used.
Concurrent
Manager Recovery Wizard
OAM managed
for recovering Concurrent Manager. It should only
be run when
the concurrent manager services are down
Cleanup
the tables
Shutdown
Application
SQL>
EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;
Deletes
data from FND_NODES and FND_OAM_CONTEXT_FILES
Run
AutoConfig
Refer below links:
How to troubleshoot long running concurrent request in
R12.2
Output post processor in concurrent manager
Concurrent manager log file locations in R12.2
How to Create a Custom Concurrent Manager in R12.2
How to assign concurrent particular concurrent program
to concurrent manager in R12.2
How to enable trace in concurrent program in R12.2
Difference between cmclean.sql and
fnd_conc_clone.setup_clean
Comments
Post a Comment