Db Session Cache Test
This test reveals whether the database session cache has been effectively utilized or not.
Target of the test : A MaxDB server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for the MaxDB server being monitored.
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The host name of the server for which the test is to be configured. |
Port |
The port number to which the server is listening. |
DatabaseName |
The test connects to a database on MaxDB and extracts performance statistics from the system tables in the database. Therefore, provide the name of a database in the DatabaseName text box. |
Username |
Since users with the SYSDBA privilege alone are allowed access to system tables, specify the name of such a user against Username. |
Password |
Provide the Password that corresponds to the specified Username. |
Confirm Password |
Confirm the password by retyping it here. |
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Cache hits |
Indicates the percentage of total database sessions that were accessed from the cache. |
Percent |
If the value of this measure is over 85%, it is a sign of good health. Values lesser than 85% might warrant a change in the cache size using the CAT_CACHE_SUPPLY parameter. The detailed diagnosis of this measure, if enabled, provides a list of session IDs, the number of attempts made to access each session, the number of times every listed session was successfully accessed from the cache, and the hit rate. |