Home › Discussions › Questions & Answers › Identifying and Managing Long Running EBS Sessions using DBA Blitz Reports

Identifying and Managing Long Running EBS Sessions using DBA Blitz Reports

Avatar photoCustomer Questions & Answers 7 replies

We are struggling with system stability caused by intermittent long running database sessions initiated by poor ad-hoc queries, sometimes running for hours and consuming critical resources. Our requirement is to Kill Long Running Sessions automatically or at least have a robust alert mechanism that identifies these runaway queries instantly so a DBA can intervene manually. How can we continuously monitor database session activity, especially those associated with EBS concurrent requests, to flag any query running beyond a predefined threshold, such as sixty minutes, and retrieve the full SQL text for analysis?

7 replies

  • Support Enginatics

    While directly automating the killing of sessions requires specific database setup, the necessary monitoring and deep diagnostics are streamlined using the DBA Blitz Reports toolkit. These reports leverage Oracle performance data to pinpoint resource-intensive sessions effectively.

  • Avatar photoCustomer

    Which specific Blitz Report diagnostic tool is best suited for identifying long-running sessions, and does it require constant real-time monitoring, or can it use existing historical data collected by Oracle?

  • Support Enginatics

    You should utilize the DBA AWR Blitz Reports, which analyze historical snapshots from the Automatic Workload Repository. This allows you to identify problematic SQL statements and their execution context over specific time periods, helping you target tuning efforts rather than reacting only in real-time.

  • Avatar photoCustomer

    Once a long-running SQL is identified through these reports, how easily can the DBA identify which functional EBS module or concurrent program initiated that query?

  • Support Enginatics

    The AWR Blitz Reports automatically correlate the technical SQL details with the corresponding functional names and responsibilities within the Oracle EBS programs. This essential link turns raw database data into actionable information for both DBA and functional teams, improving collaboration in SQL Tuning Advisory.

  • Avatar photoCustomer

    Can we configure the output of these DBA reports to be delivered automatically to the DBA team’s inbox, isolating only sessions that meet the ‘long running’ criteria?

  • Support Enginatics

    Yes, like all Blitz Reports, these diagnostic views can be scheduled as standard concurrent requests using parameters to filter for specific resource usage thresholds. The results, detailing the session and resource usage, can then be automatically emailed to the DBA team on a periodic basis.

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