Sybase DatabaseStats Test

This test is used to track the memory usage, backup state, transaction log space requests, and wait statistics of each database. For this test to work, make sure that the enable monitoring parameter is enabled.

Target of the test : A Sybase ASE server on which the MDA tables have been installed

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every Sybase ASE server being monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.


Refers to the IP address of the Sybase ASE server.


The port number at which the Sybase server listens to.


To enable this test to connect to the Sybase server and collect the required metrics, it is enough if you configure the test with the name of a Sybase user who has the “mon_role”. However, for best results, it is recommended that you configure all Sybase tests with the credentials of a Sybase user who has the “mon_role”, “sa_role’, and “sybase_ts_role”.


The password corresponding to the above user

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:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Used memory

The memory currently used by each database


Ideally, the value of this measure should be low.

In the event of a sudden slowdown in the performance of the Sybase server, you might want to compare the memory usage of all databases on the server to identify which database is excessively consuming memory resources.

Last backup state

Whether the last backup succeeded or failed. 


If the value of this measurement is ‘1’, then it indicates that the last backup you attempted or scheduled failed. You would then have to investigate the reasons for the failure and rectify them.

If the last backup was successful, then this measure will return the value ‘0’.

Transaction log state

The current status of transaction log gets.


If this measurement is ‘1’, it implies that the transaction log of that database has run out of space. When this occurs, you would have to allocate more space for that transaction log file; if not, database performance will suffer.

Append log request

The number of times the Sybase server placed a request for log space for that database.



Append log waits

The current number of log requests waiting to be processed. 


If most of the Append log requests are in waiting – i.e., if the value of this measure is dangerously close to that of the Append log requests measure- it could indicate a processing bottleneck on the server; this is typically caused by insufficient space in the transaction logs. In such a situation, it would be best to allocate more space to the transaction log, so that the request queue length reduces.