Home Discussions Questions & Answers Visibility into Currently Executing SQL for Concurrent Requests

Visibility into Currently Executing SQL for Concurrent Requests

Avatar photoCustomer January 25, 2025 at 12:49 am

We need better visibility into our currently running concurrent requests, specifically the SQL they are executing and where the time is being spent (CPU vs. IO). How can I get this data in a readable format?

Viewing 4 reply threads
  • Author
    Replies
    • Support January 26, 2025 at 12:19 am  

      Use the FND Concurrent Requests report. For performance analysis of running requests, this report provides the Session ID (SID), the currently executed SQL_ID and SQL text, and the distribution of wait time across different wait classes.

    • Avatar photoCustomer January 26, 2025 at 10:08 pm  

      If I only want to see requests that are either scheduled for the future or currently running, how do I filter the output?

    • Support January 28, 2025 at 9:24 am  

      You can use the parameter ‘Scheduled or Running’ within the FND Concurrent Requests report to specifically filter for all currently scheduled or active requests.

    • Avatar photoCustomer January 30, 2025 at 11:56 am  

      If I identify a long-running SQL_ID from this report, how can I immediately investigate its execution plan?

    • Support February 1, 2025 at 12:54 pm  

      You can take the SQL_ID and immediately run the DBA SGA SQL Execution Plan History report, entering the SQL_ID to see the execution plan currently loaded in the SGA.

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

Login with: