The optimal way to analyse Automatic Workload Repository - AWR for Oracle EBS
The Oracle’s Automatic Workload Repository (AWR) collects and maintains performance statistics for problem detection and self-tuning purposes.The report generated by AWR is typically large and requires significant years of experience to fully understand all aspects.
The process is made harder by the fact that short module codes are used and it is not clear which package and line of code needs attention. In this article we will explain the use of Enginatics AWR Blitz Reports that removes the complexity in analyzing AWR in conjunction with Oracle EBS programs.
Note that this is not comprehensive AWR guide but instead is aimed at showing you the faster way to diagnose database issues using Blitz Reports. These can be scheduled through the standard concurrent manager and emailed on a periodic basis thereby providing a reference point at all times.
It's sensible to take snapshots at fixed times so that you can gauge the typical workloads during the day, week or month end activities. Running the reports more frequently will make it easier to analyse in smaller chunks and also provide historical benchmark comparisons at each node.