The following alarms may be activated from Spotlight on SAP ASE for the server you are diagnosing. Click below to display information about each alarm.
Both topics are in Spotlight Basics
This alarm is raised if Spotlight detects an error when attempting to connect to the Backup Server. This checking is done by executing a remote server call from the connection to the Adaptive Server that Spotlight has established. Spotlight then dissects the return message from the Backup Server.
The Backup Server will need to be started by going to the host machine where the Backup Server is installed and running the appropriate shell or batch files for your environment. You will not be able to back up your database or dump your transaction logs until the respective Backup Server is up and running.
Note: If the Backup Server is down, the system will attempt to poll it. Then, if no connection can be made to the Backup Server, ASE will write a line to the Adaptive Server Error Log. You can uncheck a related option for Spotlight® on SAP ASE as described below.
If you do not want the Backup Server to be polled or checked:
Go to the main toolbar and select View -> Options -> Spotlight® on SAP ASE.
Click the check mark in the Poll Backup Server field to remove it.
This alarm is raised when the percentage of processes unable to run (waiting) because another process has a lock on a needed resource and has exceeded the defined thresholds.
The alarm thresholds are calculated as a percentage of the total number of processes running on the Adaptive Server.
Any time a process waits for another process to complete its transaction and release its locks, the overall response time and throughput for the application are affected.
Often, just an increase in the number of simultaneous users of a server may be contributing to an increase in lock contention.
A consistent trend increase warrants a detailed investigation of the locking strategy employed on the Adaptive Server.
You can research locking configuration and tuning in SAP Performance and Tuning Guide for ways to increase lock contention. Common suggestions include creating indexes (particularly on tables that have may updates and deletes) and looking for ways to keep transactions short.
Go to the Locks drilldown for specific information about the locks within an Adaptive Server.
Go to the User Activity drilldown to see detailed information about user activity.
This metric alarms as the number of current user connections approaches the maximum number defined in the configuration variable "number of user connections."
This value represents the number of connections found in the master.sysprocesses table.
If the number of connections used remains close to the maximum number allowed on the ASE, consider increasing the number of connections allowed.
There is a cost in memory associated with increasing this value (approximately 146K per connection) (ASE version dependent). Take note of the memory constraints both on the hardware and the Adaptive Server.
The "number of user connections" parameter is used to set the maximum number of discrete user connections that can be connected to Adaptive Server at the same time.
The "number of user connections" does not refer to the maximum number of processes that can be running on the ASE (i.e., the number of rows found in the sysprocesses table). That number depends not only on the value of this parameter but also on other system activity.
Go to the User Activity drilldown for more connection-related details.