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 |
---|---|---|---|---|---|
2517 | Error | 0AW13 | -867L | "Cannot change synchronization user_name when status of the last upload is unknown" | The MobiLink server uses the user_name to track synchronizations. If the status of the previous upload is unknown then you must resolve this condition before changing the user. Click here for a list of possible parameters and odbc states. |
2518 | Error | WC001 | -868L | "'%1' is an unknown character set encoding label" | The specified character set label is not recognized, so conversion from/to that character set is not possible. Click here for a list of possible parameters and odbc states. |
2519 | Error | 08W64 | -869L | "Database server cannot convert data from/to character set '%1'" | The database server cannot convert character data from/to the character set requested by the application because the character set is not supported. The connection fails. Click here for a list of possible parameters and odbc states. |
2520 | Error | WC002 | -870L | "Cannot convert between requested character set '%1' and database character set '%2'" | The server is unable to convert between the connection character set that was specified and the database character set. This could happen when the dbicu and dbicudt DLLs are not installed. Click here for a list of possible parameters and odbc states. |
2522 | Error | WP014 | -872L | "%1 does not return a result set" | A procedure called in the FROM clause of a SELECT statement must return a result set. Click here for a list of possible parameters and odbc states. |
2523 | Error | WP013 | -873L | "%1 returned multiple result sets" | A procedure called in the FROM clause of a SELECT statement cannot return multiple result sets. Click here for a list of possible parameters and odbc states. |
2524 | Error | WP015 | -686L | "Insufficient cache to start Java VM" | Insufficient cache was available to start the Java VM. Restart the database server with a larger cache size. Click here for a list of possible parameters and odbc states. |
2526 | Error | WX001 | -874L | "Column must be named: %1" | Unnamed columns cannot be used as XML element or attribute names. Name unnamed columns in the SELECT list using AS. Click here for a list of possible parameters and odbc states. |
2527 | Error | 42W73 | -875L | "There is no way to join to '%1'" | The server cannot discover a valid join condition involving this table. If the join is an outer join, you may be missing an ON clause. If the join is a KEY JOIN, the server cannot discover a foreign key-primary key relationship with this table that can be used to generate the join condition. If the join is a NATURAL JOIN, the table has no common column names with the table expression it is being joined to. Click here for a list of possible parameters and odbc states. |
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. |
2530 | Error | WT035 | -1522L | "Database needs to be upgraded to support the use of external libraries with text indexes." | The current database does not have catalog support for prefilter and term breaker external libraries. To use this feature, upgrade your database to the most recent version. 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' cannot 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. |
2537 | Error | WQ005 | -1521L | "Cannot drop a non-existing logical server membership." | Multiplex server membership about to be dropped was not found. 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. |