Home Discussions Questions & Answers Identifying Historically Slow Concurrent Programs

Identifying Historically Slow Concurrent Programs

Avatar photoCustomer July 4, 2019 at 3:55 am

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?

Viewing 4 reply threads
  • Author
    Replies
    • Support July 4, 2019 at 11:28 pm  

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

    • Avatar photoCustomer July 5, 2019 at 8:11 pm  

      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 July 7, 2019 at 2:14 am  

      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.

    • Avatar photoCustomer July 8, 2019 at 1:38 am  

      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 July 9, 2019 at 3:46 pm  

      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.

Viewing 4 reply threads
  • You must be logged in to reply to this post.

Login with: