![]() it is better to have three reports each for one hour. Split Large AWR Report into Smaller Reports: Instead of having one report for long time like one report for 3 hrs. Stick to Particular Time: You must have a specific time when Database was slow so that you can choose a shorter timeframe to get a more precise report.ģ. Collect Multiple AWR Reports: It’s beneficial to have two AWR Reports, one for the good time and other when performance is poor or you can create three reports (Before/Meantime/After reports) during the time frame problem was experienced and compare it with the time frame before and after.Ģ. To start with let us mention some high level important tips regarding AWR:ġ. Note that this is not comprehensive information and goal is to help in giving an overview of few key sections to Junior DBAs as a primer and to encourage them to build further the knowledge in related fields. Please note that explaining all sections of AWR will not be possible so we will stick to some of the most frequently used sections. In this post we will try to explain some important sections of AWR, significance of those sections and also some important tips. ![]() The report generated by AWR is a big report and it can take years of experience to actually understand all aspects of this report. ![]() The Oracle’s Automatic Workload Repository (AWR) collects, processes, and maintains performance statistics for problem detection and self-tuning purposes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |