Messages on this page are sorted by SQLSTATE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL State | Msg Type | Number | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 40W03 | Error | 2192 | -304L | "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. |
| 40W04 | Error | 2193 | -305L | "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. |
| 40W05 | Error | 2513 | -303L | "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. |
| 40W06 | Error | 2195 | -307L | "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. |
| 40W07 | Error | 2196 | -308L | "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. |
| 40W08 | Error | 2361 | -309L | "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. |
| 40W09 | Error | 2973 | -1285L | "%1 -- Transaction rolled back" | This transaction has been rolled back because the server encountered an error during a critical operation. Click here for a list of possible parameters and odbc states. |
| 42501 | Error | 2066 | -121L | "Permission denied: %1" | You do not have the required permission to perform the specified action. The message specifies the actual permission required and the object being acted upon. Click here for a list of possible parameters and odbc states. |
| 42R01 | Error | 2496 | -849L | "Referential integrity actions other than RESTRICT not allowed for temporary tables" | You attempted to specify an unsupported referential integrity action for a temporary table. Click here for a list of possible parameters and odbc states. |
| 42R02 | Error | 2497 | -850L | "Tables related by key constraint must both be permanent, or both be temporary and not created with ON COMMIT DELETE ROWS. For global temporary tables they must both be shared if one is shared." | Tables involved in a key constraint relationship must both be permanent user tables or both be temporary tables not created with ON COMMIT DELETE ROWS. Change the definition of one or both tables using ALTER TABLE. Click here for a list of possible parameters and odbc states. |
| 42R03 | Error | 2515 | -865L | "Key constraint between temporary tables requires a primary key (not unique constraint)" | The key constraint between temporary tables requires a primary key (not a UNIQUE constraint) if the database uses combined indexes. Change the definition of the primary table using ALTER TABLE or rebuild the database. Click here for a list of possible parameters and odbc states. |
| 42R04 | Error | 2904 | -1226L | "Foreign key columns do not match the primary key or a uniqueness constraint in \"%1\No message | An attempt was made to create a foreign key, but the columns specified do not match the primary key or a uniqueness constraint for the referenced table. Click here for a list of possible parameters and odbc states. |
| 42U00 | Error | 2413 | -766L | "View references '%1', which is a temporary object. Views can only refer to permanent objects" | Views must refer only to permanent objects, not to temporary objects such as local temporary tables. Click here for a list of possible parameters and odbc states. |
| 42U01 | Error | 2471 | -824L | "Illegal reference to correlation name '%1'" | Your query contains a reference in a table expression to a correlation name that is not contained in that table expression. Click here for a list of possible parameters and odbc states. |
| 42U02 | Error | 2492 | -845L | "Owner '%1' used in a qualified column reference does not match correlation name '%2'" | Your query contains a qualified column reference to a table name, but either a correlation name has been used for that table, or the owner of the table does not match the owner name specified in the column reference. Remove the owner qualification, and qualify column references only by correlation name. Click here for a list of possible parameters and odbc states. |
| 42U03 | Error | 2493 | -846L | "SET clause for column '%1' used incorrectly" | Your UPDATE statement contains an invalid SET clause, for example, there are multiple SET clauses for the same column. Click here for a list of possible parameters and odbc states. |
| 42U04 | Error | 2593 | -929L | "Constraint '%1' not found" | You misspelled the name of a constraint, or the constraint you are looking for is on a different table. Click here for a list of possible parameters and odbc states. |
| 42U05 | Error | 2594 | -930 | No message | You have asked for an unnamed column constraint to be altered, but there is at least one named constraint. Click here for a list of possible parameters and odbc states. |
| 42U06 | Error | 2601 | -937L | "Invalid reference to or operation on constraint '%1'" | You specified an invalid operation on a constraint. For example, you tried to alter a primary key constraint. Click here for a list of possible parameters and odbc states. |
| 42U07 | Error | 2634 | -970L | "Invalid hint specified for table '%1'" | A hint was specified for the current statement is not valid in this context. In a single statement, all references to a table must specify the same hint or none at all. Click here for a list of possible parameters and odbc states. |