Intro Reading and interpreting Automatic Workload Repository (AWR) reports can often seem like a daunting task, especially considering the sheer volume of information that they contain. While setting up basic monitoring and alarms for your Oracle database via the OCI console is recommended, there will come a time when a deeper understanding and interpretation of the AWR report will be required for advanced analysis. In this first part of our three-part blog series on AWR reports, we will start slow and cover some basic aspects of AWR analysis. Elapsed Time vs DB Time The first thing you should look at in your AWR report is the difference between elapsed time and DB time.High elapsed time often indicates high concurrency, where multiple sessions are running concurrently, each taking a fraction of the total time. This scenario is quite common in environments with multiple cores running in parallel, such as Exadata Cloud Service (ExaCS). Inefficient SQL queries often come to the surface h...
Information about Oracle Cloud databases and modern data platform