Messages on this page are sorted by SQLCODE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL Code | Msg Type | Number | SQL State | Message | Possible Cause |
|---|---|---|---|---|---|
| -289L | Error | 2403 | 5RW10 | "Multiple consolidated users cannot be defined" | You attempted to grant consolidated permissions when your database already has a consolidated user, or attempted to grant consolidated permissions to multiple users in a single statement. Click here for a list of possible parameters and odbc states. |
| -294L | Error | 2166 | 53W08 | "Format string argument number %1 is invalid" | 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. Click here for a list of possible parameters and odbc states. |
| -295L | Error | 2164 | 09W05 | "Cannot uniquely identify rows in cursor" | 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. Click here for a list of possible parameters and odbc states. |
| -296L | Error | 2165 | 53W07 | "Error number %1 for RAISERROR must not be less than 17000" | You supplied an invalid error number in a RAISERROR statement. The number must be greater than or equal to 17000. Click here for a list of possible parameters and odbc states. |
| -297L | Error | 2186 | 99999 | "User-defined exception signaled" | 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. Click here for a list of possible parameters and odbc states. |
| -298L | Error | 2187 | 42W22 | "Attempted two active database requests" | 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. Click here for a list of possible parameters and odbc states. |
| -299L | Error | 2188 | 57014 | "Statement interrupted by user" | You canceled a statement during its execution. The database was able to stop the operation without doing a rollback. If the statement is 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. Click here for a list of possible parameters and odbc states. |
| -300L | Error | 2189 | 40000 | "Run time SQL error -- %1" | 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. Click here for a list of possible parameters and odbc states. |
| -301L | Error | 2190 | 40W01 | "Internal database error %1 -- transaction rolled back" | An internal database error occurred. If it can be reproduced, it should be reported to iAnywhere. A ROLLBACK statement has been automatically executed. Click here for a list of possible parameters and odbc states. |
| -302L | Error | 2191 | 40W02 | "Terminated by user -- transaction rolled back" | You canceled a statement while the database was executing. A ROLLBACK statement has been automatically executed. Click here for a list of possible parameters and odbc states. |
| -303L | Error | 2513 | 40W05 | "Disk write failure '%1' -- transaction rolled back" | A disk write failed. A ROLLBACK statement has been automatically executed. Click here for a list of possible parameters and odbc states. |
| -304L | Error | 2192 | 40W03 | "Disk full '%1' -- transaction rolled back" | Your hard disk is out of space. A ROLLBACK statement has been automatically executed. Click here for a list of possible parameters and odbc states. |
| -305L | Error | 2193 | 40W04 | "I/O error %1 -- transaction rolled back" | SQL Anywhere has detected a problem with your hard disk. A ROLLBACK statement has been automatically executed. Click here for a list of possible parameters and odbc states. |
| -306L | Error | 2194 | 40001 | "Deadlock detected" | 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. Click here for a list of possible parameters and odbc states. |
| -307L | Error | 2195 | 40W06 | "All threads are blocked" | 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. Click here for a list of possible parameters and odbc states. |
| -308L | Error | 2196 | 40W07 | "Connection was terminated" | 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. Click here for a list of possible parameters and odbc states. |
| -309L | Error | 2361 | 40W08 | "Memory error -- transaction rolled back" | 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. Click here for a list of possible parameters and odbc states. |
| -311L | Error | 2208 | WI004 | "Internal rollback log corrupted" | While processing a COMMIT or ROLLBACK, corruption was found in the internal rollback log. This is a fatal internal error. Click here for a list of possible parameters and odbc states. |
| -312L | Error | 2069 | 42W34 | "User '%1' already has membership in group '%2'" | You attempted to give a membership in a group to a user that already has such membership. Click here for a list of possible parameters and odbc states. |
| -313L | Error | 2266 | 28W09 | "The login ID '%1' has not been mapped to any database user ID" | 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. Click here for a list of possible parameters and odbc states. |