This alarm is raised when the number of network packets received per second by the Adaptive Server from client connections exceeds normal volumes.
Since this metric is included in calibration, the maximum value, and thereby the alarm thresholds and flow speed, are determined by statistical sampling.
A spike in network activity could indicate:
A simple increase in the number of clients connected to an ASE
A change in the ISQL that an application is submitting to the Adaptive Server
An aberrant user connected to the Adaptive Server running an expected volume of SQL
Problems on a network could be indicated by a decrease in network activity received by an Adaptive Server coupled with a slowdown in user response times. Check with your Network Administrator.
If the current load is considered OK, but the flow and alarm rates are determined to be misleading for the load on the ASE, run calibration again for this Adaptive Server during a time frame representative of a typical workload.
Remember, packets received by an ASE is just one indication of activity on a server. Drill down to the Network page to see more detailed information about Network Activity.
Starting with Adaptive Server version 12.5.0.3, the Network drilldown can pinpoint network activity to the granularity of a user connection.
This alarm is raised when the number of network packets sent per second by the Adaptive Server to client connections exceeds normal volumes.
Since this metric is included in calibration, the maximum value, and thereby the alarm thresholds and flow speeds, are determined by statistical sampling.
A spike in network activity could indicate:
A simple increase in the number of clients connected to the ASE
A change in an application that increases the volume of result sets sent back to a client
An aberrant user connected to the Adaptive Server running unexpected SQL that is returning large result sets
Problems on a network could be indicated by a decrease in network activity sent by an Adaptive Server coupled with a slowdown in user response times. Check CPU context switching and CPU Wait detail to see if an Adaptive Server is waiting on the OS. If so, check with your Network Administrator.
If the current load is considered OK, but the flow and alarm rates are determined to be misleading for the load on the ASE, run calibration again for this Adaptive Server during a time frame representative of a typical workload.
Remember, packets sent by the ASE is just one indication of activity on a server. Drill down to the Network page to see more detailed information about Network Activity.
Starting with Adaptive Server version 12.5.0.3, the Network drilldown can pinpoint network activity to the granularity of a user connection.
This alarm is raised when Spotlight detects a user that meets or exceeds the performance criteria defined in Spotlight as being of concern.
Go to the User Activity drilldown to investigate user and process level detail concerning performance characteristics of the users connected to this Adaptive Server.
If this alarm is being raised too often, consider lowering the amount of activity level thresholds defined in Spotlight.
To customize performance criteria:
From the Spotlight menu bar, select View | Options | Spotlight® on SAP ASE | Problem User Definition.
This alarm is raised when the procedure cache hit rate for the server falls below the ranges defined by the thresholds on this component.
This hit rate is calculated as the percentage of searches that resulted in the needed query plan for a procedure being found in the procedure cache (a cache hit) when a user requests that a stored procedure be executed.
Use this data primarily to determine the effectiveness of the overall cache size for this server.
If the procedure cache is too small, a user trying to execute stored procedures or queries that fire triggers receives an error message and must resubmit the query. Space becomes available when unused plans age out of the cache.
Note: This will have a large (and negative) impact to the overall performance of the Adaptive Server.
To increase the size, see sp_configure "procedure cache size", "<new size in 2K pages>".
Use the Memory drilldown | Procedure Cache Page to find detailed information on cache utilization and a listing of objects in the stored procedure cache.*
* Available only in Adaptive Servers 12.5.0.3 or later
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center
