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
http://teachmeoracle.com/cm.html
http://teachmeoracle.com/cm02.html
In above links you can find overview of CM, How to Start/Stop CM , parameters like CONCSUB, DISPLAY, SLEEP, PMON, QUESIZ …
At http://teachmeoracle.com/cm03.html 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 adcmctl.sh or adstrtall.sh 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 adcmctl.sh 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 adcmctl.sh 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 adcmctl.sh (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 http://teachmeoracle.com/forum under Concurrent Manager Section