Sybase anomalies

The Sybase collector allows to insert the following types of anomalies in an Anomalies Profile:

Data cache hit ratio

Percentage of time a required data block is found in the data cache. This alarm is raised when the data cache hit rate falls below the ranges defined by the thresholds. When ASE Server can find the data pages it needs in the data cache, it doesn't have to perform a physical I/O. If you notice that this ratio is dropping over time, consider adding memory. The default anomaly conditions are:

Severity 1: < 99%
Severity 2: < 95%
Severity 3: < 90%

Procedure cache hit ratio

When a stored procedure is executed, percentage of searches that resulted in the needed query plan for a procedure being found in the procedure cache.

Severity 1: < 99%
Severity 2: < 95%
Severity 3: < 90%

Number of free connections

Consider Increasing the "number of user connections" configuration parameter if the number of free connections approaches 0. The default anomaly conditions are:

Severity 1: < 3 connections
Severity 2: < 2 connections
Severity 3: < 1 connections

Percentage of blocked sessions

Percentage of session which are blocked by another session. Any time a session waits for another session to complete its transaction, the overall response time for an application is affected. The default anomaly conditions are:

Severity 1: > 15 %
Severity 2: > 20 %
Severity 3: > 25 %

Percentage of CPU busy

Percentage of time that the CPU has spent doing Adaptive Server work. The default anomaly conditions are:

Severity 1: > 85 %
Severity 2: > 90 %
Severity 3: > 95 %

Percentage of CPU I/O busy

Percentage of time that Adaptive Server has spent doing input and output operations. A high value may be caused by users running IO intensive applications. Look in the "Session" tab to find those application. The default anomaly conditions are:

Severity 1: > 80 %
Severity 2: > 90 %
Severity 3: > 95 %

Percentage of locks waiting

Percentage of locks waiting to be granted. Any time a session waits for another session to complete its transaction, the overall response time for an application is affected.

Consult the Sybase's Performance and Tunning guide to help you resolve lock contention.

Creating indexes on tables on which lots of update and delete are executed can resolve the problem.
The default anomaly conditions are:

Severity 1: > 85%
Severity 2: > 90%
Severity 3: > 95%

Percentage of open databases

The configuration parameter "number of open databases" sets the maximum number of databases that can exist at one time on Adaptive Server.

To set the number of open databases parameter optimally:

The default anomaly conditions are:

Severity 1: > 90%
Severity 2: > 95%
Severity 3: > 99%

Percentage of open indexes

The configuration parameter "number of open indexes" sets the maximum number of indexes that can exist at one time on Adaptive Server.

The default run value is 500. If this number is insufficient, Adaptive Server displays a message after trying to reuse active indexes descriptors. You must adjust this value.

To set the number of open indexes parameter optimally:

The default anomaly conditions are:

Severity 1: > 90%
Severity 2: > 95%
Severity 3: > 99%

Percentage of open objects

The configuration parameter "number of open objects" sets the maximum number of objects that can exist at one time on Adaptive Server.

The default run value is 500. If this number is insufficient, Adaptive Server displays a message after trying to reuse active objects descriptors. You must adjust this value.

To set the number of open objects parameter optimally:

The default anomaly conditions are:

Severity 1: > 90%
Severity 2: > 95%
Severity 3: > 99%





Go back to the Learning center:


Copyright © AgileLoad. All rights reserved.
Agile Load testing tool| Contact AgileLoad | Terms of Use | Sitemap