eG Help

This test periodically monitors the Sybase server's error logs to promptly capture the errors that occur on the server and report the number and severity of the errors. For execution, this test requires the enable monitoring, errorlog pipe max messages, and errorlog pipe active configuration parameters to be enabled.

Measurement	Description	Measurement Unit	Interpretation
ErrorCountSeverity10_16	Indicates the number of errors with severity codes between 10 and 16, which occurred on the Sybase server during the last measurement period.	Number	Error messages with severity levels 10-16 are generated by problems that are caused by user errors. These problems can always be corrected by the user.
ErrorCountSeverity17_18	Indicates the number of errors with severity codes between 17 and 18, which occurred on the Sybase server during the last measurement period.	number	Error messages with severity level 17 mean that the command has caused Adaptive Server to run out of resources or to exceed some limit set by the System Administrator. You can continue with the work you are doing, although you may not be able to execute a particular command. The Database Owner can correct the level 17 error messages indicating that you have run out of space. Other level 17 error messages should be corrected by the System Administrator. Error messages with severity level 18 indicate some kind of internal software bug. However, the command runs to completion, and the connection to Adaptive Server is maintained. You can continue with the work you are doing, although you may not be able to execute a particular command. An example of a situation that generates severity level 18 is Adaptive Server detecting that a decision about the access path for a particular query has been made without a valid reason. Since problems that generate such messages do not keep users from their work, users tend not to report them. Users should be instructed to inform the System Administrator every time an error message with these severity levels (or higher) occur so that the System Administrator can report them.
ErrorCountSeverity19_26	Indicates the number of errors with severity codes between 19 and 26, which occurred on the Sybase server during the last measurement period.	number	Level 19: Adaptive Server fatal error in resource Error messages with severity level 19 indicate that some non-configurable internal limit has been exceeded and that Adaptive Server cannot recover gracefully. You must reconnect to Adaptive Server. Level 20: Adaptive Server fatal error in current process Error messages with severity level 20 indicate that Adaptive Server has encountered a bug in a command. The problem has affected only the current process, and it is unlikely that the database itself has been damaged. Run dbcc diagnostics. You must reconnect to Adaptive Server. Level 21: Adaptive Server fatal error in database processes Error messages with severity level 21 indicate that Adaptive Server has encountered a bug that affects all the processes in the current database. However, it is unlikely that the database itself has been damaged. Restart Adaptive Server and run the dbcc diagnostics. You must reconnect to Adaptive Server. Level 22: Adaptive Server fatal error: Table integrity suspect Error messages with severity level 22 indicate that the table or index specified in the message was previously damaged by a software or hardware problem. The first step is to restart Adaptive Server and run dbcc to determine whether other objects in the database are also damaged. Whatever the report from dbcc may be, it is possible that the problem is in the cache only and not on the disk itself. If so, restarting Adaptive Server will fix the problem. If restarting does not help, then the problem is on the disk as well. Sometimes, the problem can be solved by dropping the object specified in the error message. For example, if the message tells you that Adaptive Server has found a row with length 0 in a nonclustered index, the table owner can drop the index and re-create it.
TotalErrorCount	Indicates the total number of errors that occurred on the Sybase server during the last measurement period.	Number	Ideally, this value should be 0.