This video describes the set up and use of the Oracle monitor / collector and anomaly detector in Agile Load. In this case we set up the Oracle collector template and use another install of AgileLoad to collect the data from the database. This distributed implementation can be useful for monitoring databases where a firewall is between your machine and the target, or like in this case, the Oracle client libraries provided by Oracle do not work on the operating system you are using on your machine and you need to choose another machine with a supported OS to do the monitoring.
I am going to drag and drop my Oracle database monitoring profile and I am going to call this CoreDB, just to give it a name for the results that come back with.
The injector I am going to use is in fact a remote machine. It is another machine where I have AgileLoad installed. So I save that and then we start to run.
How to make sense of what the Oracle monitor is telling you
Go to the Oracle folder and look at the Oracle Overview.
On the overview screen I can see the monitoring summary and going across to the most commonly called sequel, I can see the most commonly called sequel statements.
Using Oracle for my anomaly list, I just click on okay and then we can see there are a number of anomalies relating to this Oracle database. So there were some monitoring graphs that we can looked at; and if you are not an Oracle expert, this can really help you.
So in this case, we can see there is an issue with a Oracle buffer cache ratio and we have a description down below of what you can do to improve that. We also have an issue with direct path IO wait time; and then scrolling down ever further, we have an issue with the index fetch ratio and what we could see there is a low value. It might mean there are a lot of table scans happening. So this is valuable information with problems on the DBA, which help you tune your Oracle database to make sure that you are getting the best out of it.