How to determine if you are getting all the benefits of Exadata via AWR

Last week Juan Loaiza introduced the latest generation of Oracle Exadata, X10M, , and with each new release comes more powerful compute power and larger flash and disk capacity. Along with all of the hardware improvements come a bunch of software enhancements that transparently accelerate your database workloads (RDMA, Smart Scan, Storage Indexes, Smart Flash Cache, etc.).

But how do you know if you are benefiting from these accelerators?

The easiest way to determine how your databases on Exadata are performing is via an Automatic Workload Repository (AWR) report, and two of my favorite Oracle experts have created step-by-step guides to help you do just that.

Cecilia Grant has written a fantastic white paper on Using AWR reports on Exadata. It provides a step-by-step guide to the Exadata performance statistics found in an AWR report and shares common challenges you may encounter and how to resolve them.

For those less familiar with Exadata, Kodi Umamageswaran(SVP of Exadata development) gave an excellent introductory talk at last year’s Oracle Database World called Transparent Performance with Exadata: What, When, How, and Why. In the session recording below, Kodi does a great job of introducing the capabilities of Exadata and how to identify those benefits using AWR to determine if you are getting all of the performance-enhancing benefits you should be.

Happy performance tuning!

Generating an AWR report for Autonomous Databases

Oracle Autonomous Database automates the lifecycle management of a database, everything from provisioning, scaling, backups and patching, but what it doesn’t do yet is fully tune your application.

You are still on the hook to make sure your app doesn’t have any concurrency bottlenecks or poorly written SQL that Auto Indexing can’t address.

So, what can you do to monitor your app while it’s running on an Autonomous Database?

The first place you can start is the Performance Hub tab on the cloud console. Here you’ll find both real-time and historical performance data in the form of Active Session History (ASH) information for the last seven days, and SQL Monitor reports for the high-load SQL. You can aggregate the ASH data several different ways including by wait class, database service, resource group or SQL ID. The same information is also available in Oracle Management Cloud (OMC), and SQL Developer Web.

But if you are trying to get a holistic view of how your app is behaving on a database, nothing beats an Automatic Workload Repository report or AWR report.

Continue reading “Generating an AWR report for Autonomous Databases”

%d bloggers like this: