Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 294 | "Format string argument number %1 is invalid" |
|---|---|
Constant | INVALID_FORMAT_STRING_ARG_NUM |
SAP Sybase Error Number | 2166 |
SQL State | 53W08 |
SQL Code | -294L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Argument number. |
Probable Cause | You supplied an invalid argument number in the format string for a PRINT or RAISERROR statement. The number must be between 1 and 20 and must not exceed the number of arguments provided. |
| Error 295 | "Cannot uniquely identify rows in cursor" |
|---|---|
Constant | CANNOT_UNIQUELY_IDENTIFY_ROWS |
SAP Sybase Error Number | 2164 |
SQL State | 09W05 |
SQL Code | -295L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You opened a UNIQUE cursor on a SELECT statement for which a set of columns uniquely identifying each row cannot be generated. One of the tables may not be defined with a primary key or uniqueness constraint, or the SELECT statement may involve a UNION, INTERSECT, EXCEPT, or GROUP BY. |
| Error 296 | "Error number %1 for RAISERROR must not be less than 17000" |
|---|---|
Constant | ERROR_NUMBER_OUT_OF_RANGE |
SAP Sybase Error Number | 2165 |
SQL State | 53W07 |
SQL Code | -296L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Error number. |
Probable Cause | You supplied an invalid error number in a RAISERROR statement. The number must be greater than or equal to 17000. |
| Error 297 | "User-defined exception signaled" |
|---|---|
Constant | USER_DEFINED_EXCEPTION |
SAP Sybase Error Number | 2186 |
SQL State | 99999 |
SQL Code | -297L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A stored procedure or trigger signaled a user-defined exception. This error state is reserved for use within stored procedures or triggers that contain exception handlers, as a way of signaling an exception that can be guaranteed to not have been caused by the database server. Valid SQLSTATE values range from 99000 to 99999 and are set by the user when executing the signal SQL statement. |
| Error 298 | "Attempted two active database requests" |
|---|---|
Constant | DOUBLE_REQUEST |
SAP Sybase Error Number | 2187 |
SQL State | 42W22 |
SQL Code | -298L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | In embedded SQL, you attempted to submit a database request while you have another request in progress. You should either use a separate SQLCA and connection for each thread accessing the database, or use thread synchronization calls to ensure that a SQLCA is only accessed by one thread at a time. |
| Error 299 | "Statement interrupted by user" |
|---|---|
Constant | INTERRUPTED |
SAP Sybase Error Number | 2188 |
SQL State | 57014 |
SQL Code | -299L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You canceled a statement during its execution. The database was able to stop the operation without doing a rollback. If the statement is an INSERT, UPDATE, or DELETE, any changes made by the statement will be canceled. If the statement is a data definition statement (for example CREATE TABLE), the statement will be canceled, but the COMMIT that was done as a side effect will not be canceled. |
| Error 300 | "Run time SQL error -- %1" |
|---|---|
Constant | ERROR |
SAP Sybase Error Number | 2189 |
SQL State | 40000 |
SQL Code | -300L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Identification of the error. |
Probable Cause | An internal database error occurred. If it can be reproduced, it should be reported to iAnywhere. You may be able to work around this problem by modifying the associated query statement. |
| Error 301 | "Internal database error %1 -- transaction rolled back" |
|---|---|
Constant | DATABASE_ERROR |
SAP Sybase Error Number | 2190 |
SQL State | 40W01 |
SQL Code | -301L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Identification of the error. |
Probable Cause | An internal database error occurred. If it can be reproduced, it should be reported to iAnywhere. A ROLLBACK statement has been automatically executed. |
| Error 302 | "Terminated by user -- transaction rolled back" |
|---|---|
Constant | TERMINATED_BY_USER |
SAP Sybase Error Number | 2191 |
SQL State | 40W02 |
SQL Code | -302L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You canceled a statement while the database was executing. A ROLLBACK statement has been automatically executed. |
| Error 303 | "Disk write failure '%1' -- transaction rolled back" |
|---|---|
Constant | DISK_WRITE_FAILED |
SAP Sybase Error Number | 2513 |
SQL State | 40W05 |
SQL Code | -303L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the file that could not be written. |
Probable Cause | A disk write failed. A ROLLBACK statement has been automatically executed. |
| Error 304 | "Disk full '%1' -- transaction rolled back" |
|---|---|
Constant | DEVICE_FULL |
SAP Sybase Error Number | 2192 |
SQL State | 40W03 |
SQL Code | -304L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the file that could not be written to the disk. |
Probable Cause | Your hard disk is out of space. A ROLLBACK statement has been automatically executed. |
| Error 305 | "I/O error %1 -- transaction rolled back" |
|---|---|
Constant | DEVICE_ERROR |
SAP Sybase Error Number | 2193 |
SQL State | 40W04 |
SQL Code | -305L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | A message describing the error that occurred. |
Probable Cause | SQL Anywhere has detected a problem with your hard disk. A ROLLBACK statement has been automatically executed. |
| Error 306 | "Deadlock detected" |
|---|---|
Constant | DEADLOCK |
SAP Sybase Error Number | 2194 |
SQL State | 40001 |
SQL Code | -306L |
ODBC 2 State | 40001 |
ODBC 3 State | 40001 |
Severity Code | |
Probable Cause | You attempted to read or write a row and it is locked by another user. Also, the other user is blocked directly or indirectly on your own transaction. This is a deadlock situation and your transaction has been chosen as the one to rollback. |
| Error 307 | "All threads are blocked" |
|---|---|
Constant | THREAD_DEADLOCK |
SAP Sybase Error Number | 2195 |
SQL State | 40W06 |
SQL Code | -307L |
ODBC 2 State | 40001 |
ODBC 3 State | 40001 |
Severity Code | |
Probable Cause | You attempted to read or write a row and it is locked by another user. Also, all other threads (see the -gn server option) are blocked waiting for a lock to be released. This is a deadlock situation and your transaction has been chosen as the one to rollback. |
| Error 308 | "Connection was terminated" |
|---|---|
Constant | CONNECTION_TERMINATED |
SAP Sybase Error Number | 2196 |
SQL State | 40W07 |
SQL Code | -308L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Your database connection has been terminated and your transaction has been rolled back. The connection may have been terminated because a DBA executed a DROP CONNECTION statement, or because the database server was shut down, or because your network connection to the database server was interrupted. |
| Error 309 | "Memory error -- transaction rolled back" |
|---|---|
Constant | MEMORY_ERROR |
SAP Sybase Error Number | 2361 |
SQL State | 40W08 |
SQL Code | -309L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The UltraLite runtime has received an unexpected error from the system calls being used to store the UltraLite database. For example, a write to persistent memory failed. This is an internal error and indicates faulty or corrupt persistent storage on the device. A ROLLBACK statement has been automatically executed. |
| Error 311 | "Internal rollback log corrupted" |
|---|---|
Constant | LOG_CORRUPTED |
SAP Sybase Error Number | 2208 |
SQL State | WI004 |
SQL Code | -311L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | While processing a COMMIT or ROLLBACK, corruption was found in the internal rollback log. This is a fatal internal error. |
| Error 312 | "User '%1' already has membership in group '%2'" |
|---|---|
Constant | ALREADY_HAS_GROUP_MEMBERSHIP |
SAP Sybase Error Number | 2069 |
SQL State | 42W34 |
SQL Code | -312L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the user that already has membership. |
Parameter 2 | Name of the group. |
Probable Cause | You attempted to give a membership in a group to a user that already has such membership. |
| Error 313 | "The login ID '%1' has not been mapped to any database user ID" |
|---|---|
Constant | LOGON_UNMAPPED |
SAP Sybase Error Number | 2266 |
SQL State | 28W09 |
SQL Code | -313L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Parameter 1 | Name of the login ID that is not mapped. |
Probable Cause | You attempted to connect using a login ID that is not mapped to a database user ID and there is no guest database user ID, or you attempted to revoke a login ID that has not been mapped. This can also occur when attempting to connect using an integrated login ID that is a member of more than one mapped group. |
| Error 503 | No message |
|---|---|
Constant | PREEMPTED |
SAP Sybase Error Number | 2260 |
SQL State | WI006 |
SQL Code | -503L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | No additional information available. |