Severity Levels 19 – 26

Fatal problems generate error messages with severity levels 19 and higher. They break the user’s connection to SAP ASE (some of the higher severity levels shut down SAP ASE). To continue working, the user must restart the client program.

When a fatal error occurs, the process freezes its state before it stops, recording information about what has happened. The process is then killed and disappears.

When the user’s connection is broken, he or she may or may not be able to reconnect and resume working. Some problems with severity levels in this range affect only one user and one process. Others affect all the processes in the database. In some cases, the system administrator must restart SAP ASE. These problems do not necessarily damage a database or its objects, but they can. They may also result from earlier damage to a database or its objects. Other problems are caused by hardware malfunctions.

Error messages from the kernel are directed to the error log file.

• Level 19: SAP ASE Fatal Error in Resource
  Error messages with severity level 19 indicate that some nonconfigurable internal limit has been exceeded and that SAP ASE cannot recover gracefully. You must reconnect to SAP ASE.
• Level 20: SAP ASE Fatal Error in Current Process
  Error messages with severity level 20 indicate that SAP ASE has encountered a bug in a command. The problem has affected only the current process, and the database is unlikely to have been damaged. Run dbcc diagnostics. The user must reconnect to SAP ASE.
• Level 21: SAP ASE Fatal Error in Database Processes
  Error messages with severity level 21 indicate that SAP ASE 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 SAP ASE and run dbcc diagnostics. The user must reconnect to SAP ASE.
• Level 22: SAP ASE Fatal Error: Table Integrity Suspect
  Error messages with severity level 22 indicate that the table or index specified in the message has been previously damaged by a software or hardware problem.
• Level 23: Fatal Error: Database Integrity Suspect
  Error messages with severity level 23 indicate that the integrity of the entire database is suspect due to previous damage caused by a software or hardware problem. Restart SAP ASE and run dbcc diagnostics.
• Level 24: Hardware Error or System Table Corruption
  Error messages with severity level 24 reflect a media failure or (in rare cases) the corruption of sysusages. The system administrator may have to reload the database. You may need to call your hardware vendor.
• Level 25: SAP ASE Internal Error
  Users do not see level 25 errors, as this level is used only for SAP ASE internal errors.
• Level 26: Rule Error
  Error messages with severity level 26 reflect that an internal locking or synchronization rule has been broken. You must shut down and restart SAP ASE.