Messages on this page are sorted by Sybase error code. Locate the appropriate code in the table below, and click the link for a full description of the message.
| Number | Msg Type | SQL State | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 2528 | Error | 08W65 | -876L | "Client out of memory" | A failure occurred when the database client was trying to allocate memory. Click here for a list of possible parameters and odbc states. |
| 2529 | Warning | 01W18 | 122L | "The result returned is non-deterministic" | FIRST or TOP n are used in a SELECT statement to limit the size of a result. The statement must also have an ORDER BY if the result is to be well-defined. If it does not have an ORDER BY, then the server is free to return any subset of the result that has the requested number of rows. Click here for a list of possible parameters and odbc states. |
| 2531 | Error | 23501 | -184L | "Column '%1' in table '%2' cannot be NULL. The invalid data was supplied to LOAD TABLE in a data file on line %3" | You either have not supplied a value where a value is required or a data conversion was necessary that resulted in a NULL value. The column definition prohibits NULL values or the column is part of a NOT NULL foreign key. Click here for a list of possible parameters and odbc states. |
| 2532 | Warning | 01W01 | 124L | "Invalid data conversion: NULL was inserted for column '%1' on row %2" | The database could not convert a value to the required type. The value being converted was supplied to the database in a data file and inserted using LOAD TABLE. A NULL value has been inserted into the column. Click here for a list of possible parameters and odbc states. |
| 2533 | Error | 53017 | -162L | "Cannot convert %1 to a %2. The bad value was supplied for column '%3' on row %4 of the data file" | The data file supplied to LOAD TABLE contains a value that cannot be converted to the required data type. Click here for a list of possible parameters and odbc states. |
| 2534 | Error | 42W09 | -877L | "SETUSER not allowed in procedures, triggers, events, or batches" | The SETUSER statement is not allowed in stored procedures, triggers, event handlers, or batches, and cannot be called from an EXECUTE IMMEDIATE statement. Click here for a list of possible parameters and odbc states. |
| 2535 | Error | 42W74 | -878L | "Index '%1' can not be clustered" | You attempted to create a clustered index (including key indexes) but the new index cannot be created, for example, because the table already has a clustered index. Click here for a list of possible parameters and odbc states. |
| 2536 | Error | WC003 | -879L | "An invalid multi-byte input character was encountered when converting from %1 to %2" | While the server was performing character set conversion on an input string, an invalid multi-byte character was encountered. The operation was aborted. Click here for a list of possible parameters and odbc states. |
| 2538 | Warning | 01WC1 | 125L | "An invalid multi-byte input character was encountered when converting from %1 to %2" | While the server was performing character set conversion on an input string, an invalid multi-byte character was encountered. The illegal character was directly copied without conversion. Data following the illegal character may be misinterpreted. See on_charset_conversion_failure option. Click here for a list of possible parameters and odbc states. |
| 2540 | Error | WC005 | -881L | "Character substitution was required when converting from %1 to %2" | While the server was performing character set conversion on an input string, some characters could not be represented in the database character set. The operation was aborted. See on_charset_conversion_failure option. Click here for a list of possible parameters and odbc states. |
| 2542 | Warning | 01WC3 | 127L | "Character substitution occurred when converting from %1 to %2" | While the server was performing character set conversion on an input string, some characters could not be represented in the database character set. Those characters were substituted. See on_charset_conversion_failure option. Click here for a list of possible parameters and odbc states. |
| 2544 | Error | WC007 | -883L | "Character conversion error or warning report is not available when the single-byte converter is used" | You attempted to set the on_charset_conversion_failure option to produce either a warning or error report. This setting is not available when the single-byte to single-byte converter is used. Click here for a list of possible parameters and odbc states. |
| 2548 | Error | 54W50 | -887L | "Virtual index creation with more than %1 columns" | You attempted to create a virtual index with more than the maximum number of columns. Click here for a list of possible parameters and odbc states. |
| 2549 | Warning | 01W20 | 129L | "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. |
| 2550 | Error | WX002 | -888L | "XML parser error: %1" | An XML instance will only parse correctly if it is well-formed as defined by the XML 1.0 specification. Click here for a list of possible parameters and odbc states. |
| 2551 | Error | 42W79 | -889L | "Statement contains an illegal usage of the non-deterministic function '%1'" | Non-deterministic functions cannot appear in a CHECK constraint, or any other type of integrity constraint. They may appear anywhere within a query, view, or derived table. However, if an aliased select list expression contains a non-determinstic function, that alias cannot be referred to elsewhere in the query. Click here for a list of possible parameters and odbc states. |
| 2552 | Error | WO002 | -657L | "Unable to connect, server definition is circular" | You attempted to connect to a remote server that maps to the local database. Click here for a list of possible parameters and odbc states. |
| 2553 | Error | 54W01 | -890L | "Statement size or complexity exceeds server limits" | The statement contains one or more constructs whose size make it impossible to process. Increasing the maximum cache size, page size, or stack size may resolve this error. Consider rewriting the query so that the internal limit is not exceeded. For example, if the query contains a large IN-list, consider inserting the IN-list's values into a temporary table. Then rewrite the query to join this temporary table to the other table(s) in the original statement. Click here for a list of possible parameters and odbc states. |
| 2554 | Error | WC008 | -891L | "Cannot convert between requested character sets '%1' and '%2'" | The server is unable to convert between the two specified character sets. This could happen when the dbicu and dbicudt DLLs are not installed. Click here for a list of possible parameters and odbc states. |
| 2555 | Error | WX003 | -892L | "XPath parser error: %1" | The XPath expression is illegal or uses features that are not currently supported. Click here for a list of possible parameters and odbc states. |