Spotlight raises an alarm when any database's transaction log exceeds the usage limits defined in the thresholds.
The container and the percentage figure are for the database listed whose transaction log has the highest level of used space.
There are several options:
If the transaction log and the data are on the same device, run an "alter database" command and increase the size of the transaction log. (Go to the Devices drilldown to see space available on each device.)
If the transaction log is on a separate device, run "sp_extendsegment" to extend the logsegment to another device. (Go to the Devices drilldown to see space available on each device.)
Reduce the size of the transaction log being used by making a copy of a transaction log and removing the inactive portion. This is done by dumping the transaction log (dump tran <database name> <options>).
Go to the Databases drilldown to see space and capacity metrics for each database.
This alarm is raised when the percentage of time that the Adaptive Server's Host CPU has been performing tasks exceeds the defined thresholds.
By drilling down to the associated SoWin or SoUNIX plug ins, you may be able to identify and correct the cause of the high CPU usage.
This alarm is raised when the percentage of time that the Adaptive Server's CPU was performing Adaptive Server I/O-related tasks has crossed a defined threshold.
A high value may just be caused by one or more users running an I/O-intensive application or an unscheduled batch job running. Go to the Users drilldown and sort on I/O to determine which processes are consuming the most I/O.
If values are consistently very high, it is likely that response time and throughput could benefit from additional devices or better distribution of I/O among multiple devices.
Go to the Devices drilldown and note the performance characteristics of the devices defined to this Adaptive Server.
This alarm is raised when the number of locks waiting to be granted is above normal levels.
Since this metric is included in calibration, the maximum value, and thereby the alarm thresholds, are determined by statistical sampling.
Often just an increase in the number of simultaneous users of a server may be contributing to an increase in lock utilization.
If a server runs out of locks, a server message will be written to the Error Log, and the application that a user is running can fail.
While there is a slight cost in memory (approximately 150 bytes per lock) to increase the number of locks on a server, this cost is minimal.
To determine exactly how much additional memory will be needed, go to Spotlight's Memory drilldown | Configuration page and select "number of locks." Then, enter a speculative value. Spotlight will return the cost in memory that the increase will incur.
Use SAP system stored procedure to increase the number of locks.
sp_configure "number of locks," <new value>
Depending on the number of locks newly configured, you may need to increase the "total memory" configuration parameter as well.
Refer to SAP Performance and Tuning Guide for a comprehensive section on configuring Adaptive Server's lock limit.
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.