Home Discussions Questions & Answers Database CPU Spikes: Finding the Culprit SQL

Database CPU Spikes: Finding the Culprit SQL

Avatar photoCustomer February 5, 2022 at 5:05 pm

We are experiencing significant CPU spikes on our database server every morning, causing slowdowns across EBS. How can I quickly pinpoint the specific SQL statements responsible for this high load?

Viewing 4 reply threads
  • Author
    Replies
    • Support February 7, 2022 at 7:11 am  

      You should run the DBA AWR SQL Performance Summary report. This report retrieves summarized execution statistics, focusing on CPU-intensive SQLs, as the default sorting prioritizes maximizing server load optimization.

    • Avatar photoCustomer February 8, 2022 at 11:40 pm  

      Which columns in the report should I focus on to confirm CPU consumption, and how can I narrow down the time frame to match our morning spike?

    • Support February 10, 2022 at 11:11 pm  

      Look primarily at the ‘Cpu Time’ and ‘Buffer IO’ columns; high CPU time often indicates massive amounts of data read from the buffer cache. To target the time window, ensure you filter the report using the snapshot interval parameters corresponding to your morning peak hours.

    • Avatar photoCustomer February 13, 2022 at 1:33 am  

      If the problem SQL is highly CPU intensive, is that a sure sign of inefficient query logic?

    • Support February 13, 2022 at 10:44 pm  

      High CPU time suggests the SQL is reading a lot of data, often due to poor indexing or full table scans. You can drill down using the SQL_ID and Plan Hash Value to analyze the execution path using DBA SGA SQL Execution Plan History.

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

Login with: