Home › Discussions › Questions & Answers › Identifying Historically Slow Concurrent Programs

Identifying Historically Slow Concurrent Programs

Avatar photoCustomer Questions & Answers 5 replies

We need to identify which concurrent programs consume the most time cumulatively over the last year. Which Blitz Report should we use to get a historical summary of execution times?

5 replies

  • Support Enginatics

    You should utilize the FND Concurrent Requests Summary report. This report lists concurrent programs sorted by the sum of their historic execution times.

  • Once I identify a problematic program, how can I delve into its individual runs to see if a specific run caused the high total time?

  • Support Enginatics

    You can transition to the FND Concurrent Requests report. This report shows detailed information for historic requests, including execution timing, parameters, the status, and the currently executed SQL_ID and SQL text for running requests.

  • We suspect one program might be suffering due to frequent waiting time before starting. Can I assess the queue waiting time using these reports?

  • Support Enginatics

    Yes. The underlying data for Concurrent Request summaries typically includes metrics on the requested start date versus the actual start date, allowing you to calculate or see the average time spent waiting in the queue. For tuning concurrent manager waiting periods, remember to check manager definitions using FND Concurrent Managers.

  • You must be logged in to reply to this post.