|
Measures reported by SybDBStatsTest
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.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Tot_mem_usage |
The memory currently used by each database. |
MB |
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. |
| LastBackupState |
Indicates whether the last backup succeeded or failed. |
number |
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’. |
| TransactionLogState |
Indicates the current status of transaction log gets. |
number |
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. |
| AppendLogRequest |
Indicates the number of times the Sybase server placed a request for log space for that database. |
number |
|
| AppendLogWaits |
Indicates the current number of log requests waiting to be processed. |
number |
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. |
|