Concurrent Manager Troubleshooting Flowchart

Concurrent Manager Troubleshooting Flowchart

There have been some really good notes on concurrent managers. And also a couple on troubleshooting concurrent Managers.

When it comes to troubleshooting concurrent managers in my case i used a flowchart based approach which always worked in most cases.

I made this one based on a similar one for workflow which i had seen sometime back.I believe that most you guys would already be following a similar approach. I just found it easier to put it up in a flow chart format to help me out.

In case you found that confusing or messy here is an explanation of the approach.

• Submit a Standard Concurrent Report and check if it completes successfully.


• Check if you are able to view the log/output file if not check if your APPS listener is running.


• If your concurrent report fails check the log report or request log file.


• Check if your standard manager is running from the front end.


• Check if the internal concurrent manager is up and running.


• Check the UNIX background process of your concurrent manager
  
  ps -ef|grep FNDLIBR.


• Check your Concurrent Manager log files at $APPLCSF/$APPLLOG.


• If the managers are failing due a problematic request try running cmclean.sql or use the recover concurrent manager option from Oracle Applications Manager.


• In case your concurrent managers are not able to start due to failing to accuire locks, try clearing up the locks from the database.


• If you are still having trouble with your concurrent managers you can try re creating the concurrent manager views using
  
  FNDLIBR  FND  FNDCPBWV  apps/<passwd>  SYSADMIN  ‘System Administrator’  SYSADMIN

Concurrent Manager Troubleshooting Flowchart