oracle, February 03, 2016 - 7:01 am UTC
Thanks for your quick reply,
I have gone through the awr related docs but it is more high which i am expecting because i want awr report with each section description to check how read and when the section is high/low then what we will be the case of and what is the solution .
Thanks
February 04, 2016 - 4:01 am UTC
Each of those presentations starts high level and gives the appropriate *definitions" that control what you should be looking for in AWR reports (and/or OEM).
It's not about "check how to read and when the section is high/low"... its about what *defines* the performance of my system with respect to the things that define my business responsibilities (eg user response times, nightly load throughput etc).
Understand the terms and concepts in those whitepapers and the sections will take care of themselves.
How to read explain plan
Rajeshwaran, Jeyabal, February 03, 2016 - 8:12 am UTC
wrong approach
Jeff, February 03, 2016 - 7:50 pm UTC
"Currently i am generating AWR Report and check the top 10 queries and generate the execution plan for that queries and check full table scan and ask to the application team to tune this queries then they create an index and tune queries accordingly. After that tunning again i check the execution plan to verify that the full table scan is not now. "
No.
Tablescans are not necessarily bad.
Index lookups are not necessarily good.
There is so much more to tuning SQL than "get rid of the tablescans".
February 04, 2016 - 2:35 am UTC
yup