Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Warning 129 | "Plan may contain virtual indexes" |
|---|---|
Constant | USING_VIRTUAL_INDEXES |
SAP Sybase Error Number | 2549 |
SQL State | 01W20 |
SQL Code | 129L |
ODBC 2 State | 01S01 |
ODBC 3 State | 01S01 |
Severity Code | |
Probable Cause | Virtual indexes are currently enabled in this connection. Any plans that are generated may contain virtual indexes. |
| Warning 130 | "A row was dropped because it could not be converted to the new schema format" |
|---|---|
Constant | ROW_DROPPED_DURING_SCHEMA_UPGRADE |
SAP Sybase Error Number | 2559 |
SQL State | 01W21 |
SQL Code | 130L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | 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 cannot be cast to the new domain. Rows are also dropped if a uniqueness or foreign key constraint cannot be satisfied. |
| Error 130 | "Invalid statement" |
|---|---|
Constant | INVALID_STATEMENT |
SAP Sybase Error Number | 2070 |
SQL State | 07W02 |
SQL Code | -130L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The prepared statement is invalid. In embedded SQL, an OPEN or EXECUTE failed. |
| Error 131 | "Syntax error near '%1' %2" |
|---|---|
Constant | SYNTAX_ERROR |
SAP Sybase Error Number | 2071 |
SQL State | 42W04 |
SQL Code | -131L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | The word or symbol where the syntax error has been detected. |
Parameter 2 | Line number. |
Probable Cause | 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"). |
| Error 132 | "SQL statement error" |
|---|---|
Constant | STATEMENT_ERROR |
SAP Sybase Error Number | 2073 |
SQL State | 26501 |
SQL Code | -132L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The prepared statement identifier is invalid. In embedded SQL, an OPEN or EXECUTE failed. |
| Warning 132 | "Cannot output the histogram for string column '%1'" |
|---|---|
Constant | CANNOT_DUMP_STRING_HISTOGRAM |
SAP Sybase Error Number | 2562 |
SQL State | 01W23 |
SQL Code | 132L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | Name of the column containing string data. |
Probable Cause | 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. |
| Error 133 | "Invalid prepared statement type" |
|---|---|
Constant | INVALID_STATEMENT_TYPE |
SAP Sybase Error Number | 2074 |
SQL State | 07W03 |
SQL Code | -133L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | This is an internal error. If it can be reproduced, it should be reported to iAnywhere. |
| Warning 133 | "UltraLite connection was restored" |
|---|---|
Constant | CONNECTION_RESTORED |
SAP Sybase Error Number | 2635 |
SQL State | WW040 |
SQL Code | 133L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | The connection attempt completed successfully and the transaction was restored from a suspended state. |
| Error 134 | "Feature '%1' not implemented" |
|---|---|
Constant | NOT_IMPLEMENTED |
SAP Sybase Error Number | 2075 |
SQL State | 0A000 |
SQL Code | -134L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The unimplemented feature. |
Probable Cause | You attempted to carry out an operation or use a feature that is not implemented in this version of SQL Anywhere. In UltraLite, this error often occurs because you attempted to perform an unsupported operation on a LONG VARCHAR or LONG BINARY column. For example, the SUBSTRING function cannot be used with a LONG VARCHAR column. As well, an index cannot be created on a LONG column. |
| Warning 134 | "UltraLite cursor (or result set or table) was restored" |
|---|---|
Constant | CURSOR_RESTORED |
SAP Sybase Error Number | 2636 |
SQL State | WW041 |
SQL Code | 134L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | The cursor (or result set or table) was opened successfully and the cursor position was restored from the suspended state. |
| Error 135 | "Language extension" |
|---|---|
Constant | LANGUAGE_EXTENSION |
SAP Sybase Error Number | 2077 |
SQL State | 0AW01 |
SQL Code | -135L |
ODBC 2 State | 37000 |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You used a SQL statement that may be valid in some versions of SQL, but not in SQL Anywhere. |
| Error 136 | "Table '%1' is in an outer join cycle" |
|---|---|
Constant | OUTER_JOIN_CYCLE |
SAP Sybase Error Number | 2088 |
SQL State | 52W14 |
SQL Code | -136L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of a table in the cycle. |
Probable Cause | You specified outer joins that create a cycle of tables. |
| Warning 136 | "The database was created" |
|---|---|
Constant | DATABASE_CREATED |
SAP Sybase Error Number | 2666 |
SQL State | WW061 |
SQL Code | 136L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | The specified UltraLite database was created using the specified schema when the connection was opened. |
| Error 137 | "Table '%1' requires a unique correlation name" |
|---|---|
Constant | CORRELATION_NAME_NEEDED |
SAP Sybase Error Number | 2090 |
SQL State | 52W15 |
SQL Code | -137L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the table that needs a unique correlation name. |
Probable Cause | You specified a join that joins a table to itself. You need to use unique correlation names to have multiple instances of a table. |
| Warning 137 | "Row was dropped from table %1 to maintain referential integrity" |
|---|---|
Constant | ROW_DELETED_TO_MAINTAIN_REFERENTIAL_INTEGRITY |
SAP Sybase Error Number | 2690 |
SQL State | 01W24 |
SQL Code | 137L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | The name of the table. |
Probable Cause | A delete of a primary row during a download forced its foreign row(s) to also be deleted to maintain referential integrity. |
| Error 138 | "Dbspace '%1' not found" |
|---|---|
Constant | DBSPACE_NOT_FOUND |
SAP Sybase Error Number | 2078 |
SQL State | 52W13 |
SQL Code | -138L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the dbspace that could not be found. |
Probable Cause | You tried to access a dbspace that the database server could not find. |
| Warning 138 | "Publication predicates were not evaluated" |
|---|---|
Constant | PUBLICATION_PREDICATE_IGNORED |
SAP Sybase Error Number | 2761 |
SQL State | 01W25 |
SQL Code | 138L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | 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. |
| Error 139 | "More than one table is identified as '%1'" |
|---|---|
Constant | CORRELATION_NAME_AMBIGUOUS |
SAP Sybase Error Number | 2079 |
SQL State | 52012 |
SQL Code | -139L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Ambiguous correlation name. |
Probable Cause | You identified two tables in the same FROM clause with the same correlation name. |
| Warning 139 | "Option '%1' specified more than once" |
|---|---|
Constant | DUPLICATE_OPTION |
SAP Sybase Error Number | 2770 |
SQL State | 01W26 |
SQL Code | 139L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | The name of the duplicated option. |
Probable Cause | A particular option has been specified multiple times. Only the last instance of the option is used; the previous ones are ignored. |
| Error 140 | "User ID '%1' does not exist" |
|---|---|
Constant | UNKNOWN_USERID |
SAP Sybase Error Number | 2080 |
SQL State | 08004 |
SQL Code | -140L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Parameter 1 | Name of the user that could not be found. |
Probable Cause | You used a user ID that does not exist. |