Thisismarkantony.com

This is the third and final part of this blogpost series, I would strongly recommend to go through the  Part-I  &  Part-II  of this series if you have directly landed to this post. In  Part-II , we identified the SQL statements which were the main contributors for USER I/O. In this post we will learn how to reduce the DB_Time considerably. In short, let try to explore the opportunities to reduce the  Where, DB_Time = CPU Time + Non-Idle Wait time ( If you are new to these matrices, I would recommend you to get quick web trainings from Craig Shallahamer from OraPub ) We will use SQL Tuning Advisor to find out for some advice.  1) Below screenshot is again of the ASH Analytics home screen for my database.  As we can see there are a couple of SQL Statements that cause the major part of the activity. You should see top SQL id. Select top three SQL's,  Please Note: Ignore below screenshot which has top five selected an...

This is the second part of the blogpost series, I would strongly recommend to go through the  Part-I  of this series if you have directly landed to this post. In this Part-II, I will be explaining on how to use the ASH Analytics + SQL Performance Analyzer(SPA) together and quickly arrive at the story that can be used to explain your management about the database performance issues. Not restricting us with only stories, We can further give birth to validated solutions/fix for the performance issue....Yes I said...."VALIDATED SOLUTION/FIX". This will be in Part-III Now let's see how to quickly identify the performance issues and drill down in few seconds & few navigation. Just follow the screenshots and the orange boxes. 1) You would have noticed the same screenshot was in the tail end of  Part-I  Just proving that this is the sequential post ;) This is the ASH Analytics screen, and I will be concentrating on the highlighted portion of this ASH graph....

Oracle Enterprise Manager 12c Grid Control, Jump into SPA- Part I Reading my below blogposts would give you the similar feeling when you want to encounter the performance issues in your production database environments. SPA stands for "SQL Performance Analyzer", Which perfectly inteegrates with our existing utilities like AWR, ADDM & SPM etc to provide a very easy manageable interface to solve the performance issues. SPA uses the method of  FIND-VALIDATE-FIX  SPA is only available from OEM 12c (12.1.3) version.   Oracle Enterprise Manager 12c Grid Control, Jump into SPA- Part I Oracle Enterprise Manager 12c Grid Control, Jump into SPA- Part II Oracle Enterprise Manager 12c Grid Control, Jump into SPA- Part III Part-I will show on how to install the ASH Analytics plugin (Because in my case ASH Analytics Plugin was not installed in my target database), Which is the major instrument we will be using for diagnosing the performance issues effectively....