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 |
|---|---|---|---|---|---|
| 2FW88 | Error | 3169 | -1501L | "Invalid bounds for coordinate %1 (near \"BETWEEN %2 AND %3\")" | The specified coordinate bounds are not valid. Click here for a list of possible parameters and odbc states. |
| 2FW89 | Error | 3170 | -1502L | "ST_MultiSurface contains elements with an invalid intersection (near \"%1\")" | The interiors of any two ST_Surface values in an ST_MultiSurface shall not intersect. The boundaries of any two elements in an ST_MultiSurface may intersect at a finite number of points (and not, for example, in a line segment). Click here for a list of possible parameters and odbc states. |
| 2FW90 | Error | 3171 | -1503L | "Operation not supported for ST_GeomCollection with intersecting elements (near \"%1\")" | The ST_GeomCollection contains elements that intersect in a way that is not valid for an ST_MultiSurface. The operation is not supported for this kind of geometry. Click here for a list of possible parameters and odbc states. |
| 2FW91 | Error | 3179 | -1515L | "Support for spatial is not available for this CPU." | Spatial data support for 32-bit Windows and 32-bit Linux requires a CPU that supports the SSE2 instructions. Click here for a list of possible parameters and odbc states. |
| 2FW92 | Error | 3186 | -1531L | "Geometry expressions cannot be used in the ORDER BY specification (near '%1')" | Geometry expressions cannot be used in the ORDER BY clause. The ST_LinearHash() method may be used in the ORDER BY specification to order geometry values using the same rules used for spatial indexes, or a conversion method such as ST_AsText() may be used to order the rows by their string representation. Click here for a list of possible parameters and odbc states. |
| 33000 | Error | 2248 | -642L | "Invalid SQL descriptor name" | You attempted to deallocate a descriptor that has not been allocated. Click here for a list of possible parameters and odbc states. |
| 37505 | Error | 2100 | -154L | "Wrong number of parameters to function '%1'" | You supplied an incorrect number of parameters to a database function. Click here for a list of possible parameters and odbc states. |
| 38W01 | Error | 2575 | -910L | "System command failed with return code %1" | A non-zero return code resulted when executing a system command. Click here for a list of possible parameters and odbc states. |
| 3B001 | Error | 2174 | -220L | "Savepoint '%1' not found" | You attempted to rollback to a savepoint that does not exist. Click here for a list of possible parameters and odbc states. |
| 3B002 | Error | 2175 | -221L | "ROLLBACK TO SAVEPOINT not allowed" | You attempted a ROLLBACK TO SAVEPOINT within an atomic operation to a savepoint established before the atomic operation. Click here for a list of possible parameters and odbc states. |
| 3BW01 | Error | 2177 | -213L | "Savepoints require a rollback log" | You cannot use savepoints when the database server is running in bulk mode without a rollback log. Click here for a list of possible parameters and odbc states. |
| 3BW02 | Error | 2176 | -222L | "Result set not allowed from within an atomic compound statement" | You used a SELECT statement with no INTO clause or a RESULT CURSOR statement within an atomic compound statement. Click here for a list of possible parameters and odbc states. |
| 40000 | Error | 2189 | -300L | "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. |
| 40001 | Error | 2194 | -306L | "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. |
| 40W01 | Error | 2190 | -301L | "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. |
| 40W02 | Error | 2191 | -302L | "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. |
| 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. |