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 |
|---|---|---|---|---|---|
| 129L | Warning | 2549 | 01W20 | "Plan may contain virtual indexes" | Virtual indexes are currently enabled in this connection. Any plans that are generated may contain virtual indexes. Click here for a list of possible parameters and odbc states. |
| 130L | Warning | 2559 | 01W21 | "A row was dropped because it could not be converted to the new schema format" | A row that was valid in the old schema is no longer valid. This could be because a column domain changed and the old value can not be cast to the new domain. Rows are also dropped if a uniqueness or foreign key constraint cannot be satisfied. Click here for a list of possible parameters and odbc states. |
| -130L | Error | 2070 | 07W02 | "Invalid statement" | The statement identifier generated by a PREPARE passed to the database for a further operation is invalid. Click here for a list of possible parameters and odbc states. |
| -131L | Error | 2071 | 42W04 | "Syntax error near '%1' %2" | The database server cannot understand the statement you are trying to execute. If you used a keyword (such as DATE) for a column name, try enclosing the keyword in quotation marks ("DATE"). Click here for a list of possible parameters and odbc states. |
| -132L | Error | 2073 | 26501 | "SQL statement error" | The statement identifier (generated by PREPARE) passed to the database for a further operation is invalid. Click here for a list of possible parameters and odbc states. |
| 132L | Warning | 2562 | 01W23 | "Cannot output the histogram for string column '%1'" | You tried to get the histogram for a column containing strings. Histograms on string information cannot be output in a readable format; as a result, no information was retrieved. Consider using the ESTIMATE function to get information on a specific value or range in the column. Click here for a list of possible parameters and odbc states. |
| -133L | Error | 2074 | 07W03 | "Invalid prepared statement type" | This is an internal error. If it can be reproduced, it should be reported to iAnywhere. Click here for a list of possible parameters and odbc states. |
| 133L | Warning | 2635 | WW040 | "UltraLite connection was restored" | The connection attempt completed successfully and the transaction was restored from a suspended state. Click here for a list of possible parameters and odbc states. |
| -134L | Error | 2075 | 0A000 | "Feature '%1' not implemented" | You attempted to carry out an operation or use a feature that is not implemented in this version of SQL Anywhere. Click here for a list of possible parameters and odbc states. |
| 134L | Warning | 2636 | WW041 | "UltraLite cursor (or result set or table) was restored" | The cursor (or result set or table) was opened successfully and the cursor position was restored from the suspended state. Click here for a list of possible parameters and odbc states. |
| -135L | Error | 2077 | 0AW01 | "Language extension" | You used a SQL statement that may be valid in some versions of SQL, but not in SQL Anywhere. Click here for a list of possible parameters and odbc states. |
| -136L | Error | 2088 | 52W14 | "Table '%1' is in an outer join cycle" | You specified outer joins that create a cycle of tables. Click here for a list of possible parameters and odbc states. |
| 136L | Warning | 2666 | WW061 | "The database was created" | The specified UltraLite database was created using the specified schema when the connection was opened. Click here for a list of possible parameters and odbc states. |
| -137L | Error | 2090 | 52W15 | "Table '%1' requires a unique correlation name" | You specified a join that joins a table to itself. You need to use unique correlation names in order to have multiple instances of a table. Click here for a list of possible parameters and odbc states. |
| 137L | Warning | 2690 | 01W24 | "Row was dropped from table %1 to maintain referential integrity" | A delete of a primary row during download forced its foreign row(s) to be deleted as well to maintain referential integrity Click here for a list of possible parameters and odbc states. |
| -138L | Error | 2078 | 52W13 | "Dbspace '%1' not found" | You tried to access a dbspace that the database server could not find. Click here for a list of possible parameters and odbc states. |
| 138L | Warning | 2761 | 01W25 | "Publication predicates were not evaluated" | Publication predicates were not evaluated because UltraLite was initialized without SQL support. The table will be uploaded as if no publication predicate was specified for the table. Click here for a list of possible parameters and odbc states. |
| -139L | Error | 2079 | 52012 | "More than one table is identified as '%1'" | You identified two tables in the same FROM clause with the same correlation name. Click here for a list of possible parameters and odbc states. |
| 139L | Warning | 2770 | 01W26 | "Option '%1' specified more than once" | A particular option has been specified multiple times. Only the last instance of the option is used; the previous ones are ignored. Click here for a list of possible parameters and odbc states. |
| -140L | Error | 2080 | 08004 | "User ID '%1' does not exist" | You used a user ID that does not exist. Click here for a list of possible parameters and odbc states. |