| Measurement |
Description |
Measurement Unit |
Interpretation |
| Availability |
Indicates whether the database instance is responding to requests. |
Percent |
The availability is 100% when the instance is responding to a request and 0% when it is not. Availability problems may be caused by a misconfiguration/malfunctioning of the database instance, or because the instance is using an invalid user account. Besides the above, this measure will report that the server is unavailable even if a connection to the database instance is unavailable, or if a query to the database fails. In this case, you can check the values of the Conn_availability and Query_availability measures to know what is exactly causing the database instance to not respond to requests - is it owing to a connection unavailability? or is it due to a query failure? |
| Response_time |
Indicates the time taken by the database to respond to a user query. This is the sum total of the connection time and query execution time. |
Secs |
A sudden increase in response time is indicative of a bottleneck at the database server. This could even be owing to a connection delay and/or long running queries to the database. Whenever the value of this measure is high, it would be good practice to compare the values of the Conn_resp_time and Query_resp_time measures to zero-in on the root-cause of the poor responsiveness of the server - is it because of connectivity issues? or is it because of inefficient queries? |
| Conn_availability |
Indicates whether the database connection is available or not. |
Percent |
If this measure reports the value 100, it indicates that the database connection is available. The value 0 on the other hand indicates that the database connection is unavailable. A connection to the database may be unavailable if the database is down or if the database is listening on a port other than the one configured for it in the eG manager or owing to a poor network link. If the Oracle server availability measure reports the value 0, then, you can check the value of this measure to determine whether/not it is due to the unavailability of a connection to the server. |
| Conn_resp_time |
Indicates the time taken by the database connection. |
Secs |
A high value could indicate a connection bottleneck. Whenever the Response_time of the measure soars, you may want to check the value of this measure to determine whether a connection latency is causing the poor responsiveness of the server. |
| Query_availability |
Indicates whether the database query is executed successfully or not. |
Percent |
If this measure reports the value 100, it indicates that the query executed successfully. The value 0 on the other hand indicates that the query failed. In the event that the Availability measure reports the value 0, check the value of this measure to figure out whether the failed query is the reason why that measure reported a server unavailability. |
| Query_resp_time |
Indicates the time taken for query execution. |
Secs |
A high value could indicate that one/more queries to the database are taking too long to execute. Inefficient/badly designed queries to the database often take too long to execute. If the value of this measure is higher than that of the Connection time measure, you can be rest assured that long running queries are causing the respond slowly to requests. |
| Number_of_records |
Indicates the number of records fetched from the database. |
Number |
The value 0 indicates that no records are fetched from the database. |