Error Severity Sybase

caused by user errors. These problems can be corrected by the user. Severity levels 17 and 18 do not terminate the user’s session. Error messages with severity levels 17 and higher should be reported to the system administrator or database owner. Level 10: Status Information Messages with severity level 10 provide additional information after certain commands have been executed and, typically, do not display the message number or severity level. Level 11: Specified Database Object Not Found Messages with severity level 11 indicate that SAP ASE cannot find an object that is referenced in a command. Level 12: Wrong Datatype Encountered Messages with severity level 12 indicate a problem with datatypes. For example, the user may have tried to enter a value of the wrong datatype in a column or to compare columns of different and incompatible datatypes. Level 13: User Transaction Syntax Error Messages with severity level 13 indicate that something is wrong with the current user-defined transaction. Level 14: Insufficient Permission to Execute Command Messages with severity level 14 mean that the user does not have the necessary permission to execute the command or access the database object. Users can ask the owner of the database object, the owner of the database, or the system administrator to grant them permission to use the command or object in question. Level 15: Syntax Error in SQL Statement Messages with severity level 15 indicate that the user has made a mistake in the syntax of the command. The text of these error messages includes the line numbers on which the mistake occurs and the specific word near which it occurs. Level 16: Miscellaneous User Error Most error messages with severity level 16 reflect that the user has made a nonfatal mistake that does not fall into any of the other categories. Severity level 16 and higher might also indicate software or hardware errors. Level 17: Insufficient Resources Error messages with severity

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 http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc31654.1600/doc/html/san1360629238802.html 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 http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc31654.1600/doc/html/san1360629243052.html 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.

object id, current marker (%d, %d). Explanation: Internal error, affects current process. Contact your SA. 9202 20 %S_REPAGNT: http://infocenter-archive.sybase.com/help/topic/com.sybase.39996_1250/html/svrtsg/svrtsg360.htm Nested replicated stored procedure detected. Transaction log may be corrupt. Please http://infocenter-archive.sybase.com/help/topic/com.sybase.39996_1250/html/svrtsg/svrtsg388.htm contact SYBASE Technical Support. (current marker = %d, %d) Explanation: Internal error, affects current process. Contact your SA. 9203 20 %S_REPAGNT: Encountered an End Transaction that was not in abort state while locating after image for Delete at (%d, %d), transaction = (%d, error severity %d). Explanation: Internal error, affects current process. Contact your SA. 9204 20 %S_REPAGNT: Could not locate schema for object with id = (%d), current marker (%d , %d). Explanation: Internal error, affects current process. Contact your SA. 9205 20 %S_REPAGNT: A replicated End Stored Procedure Execution log record was found with out a Begin. Transaction error severity sybase log may be corrupt. Please contact SYBASE Technical Support. objid = (%d), current marker = (%d, %d) Explanation: Internal error, affects current process. Contact your SA. 9206 20 %S_REPAGNT: Error initializing the Rep Agent. Could not set affinity to engine (% d). Explanation: 9207 20 %S_REPAGNT: Could not re-read XCMDTEXT log record at (%d, %d), current marker (%d , %d). Explanation: Internal error, affects current process. Contact your SA. 9208 20 %S_REPAGNT: Update detected within a subscribable function. Transaction log may be corrupt. Please contact SYBASE Technical Support. (current marker = (%d, %d)). Explanation: Internal error, affects current process. Contact your SA. 9209 20 %S_REPAGNT: Missing datarow in TEXT/IMAGE insert log record. Transaction log may be corrupt. Please contact SYBASE Technical Support. (current marker = (%d, %d)). Explanation: Internal error, affects current process. Contact your SA. 9210 20 %S_REPAGNT: Fatal error from CT-Lib. (CT-Lib command = %s, return status = %d). Explanation: Internal error, affects current process. Contact your SA. 921

the forwarded row (%d, %d) pointed to by (%d, %d) is invalid. Aborting the transaction. Explanation: Adaptive Server encountered an internal error affecting the current process. Reconnect to Adaptive Server. Report the error to your System Administrator so DBCC diagnostics can be run. 12301 20 Internal error: the index (id = %d) and the data for row (%d, %d) in table '%.*s', database %d are inconsistent; data is marked deleted but index is not. Aborting the tran saction. Explanation: Adaptive Server encountered an internal error affecting the current process. Reconnect to Adaptive Server. Report the error to your System Administrator so DBCC diagnostics can be run. 12302 20 Internal error: deleted row (%d, %d) erroneously qualified for table '%.*s', database %d. Terminating the scan. Explanation: Adaptive Server encountered an internal error affecting the current process. Reconnect to Adaptive Server. Report the error to your System Administrator so DBCC diagnostics can be run. 12303 20 Internal error: invalid scan branch type. Aborting the transaction. Explanation: Adaptive Server encountered an internal error affecting the current process. Reconnect to Adaptive Server. Report the error to your System Administrator so DBCC diagnostics can be run. 12304 10 Index id %d cannot be used to access table id %d as it is SUSPECT. Please drop and re-create the index. Table-scan is being used instead. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message. 12306 26 No table lock on object '%.*s' in database '%.*s'. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server. 12307 26 Row %d of Page %ld in table ’%.*s’ (id = %ld) in dbid %d is not locked. Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adapt