Messages 2528 through 2548

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.

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.

2539 Error WQ004 -1520L "Cannot recreate an already existing logical server membership." Multiplex server which is to be added as a member is already a member of logical server.

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.

2541 Error WQ003 -1519L "Cannot perform the requested operation due to overlapping logical server memberships for login policy \"%1\"." Cannot perform the requested operation since this would result in an overlapping logical server membership for named login policy.

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.

2543 Error WQ002 -1518L "Logical Server Policy \"%1\" does not allow coordinator membership in logical servers." Logical server policy does not allow coordinator as a member of logical server.

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.

2545 Error WQ001 -1517L "Logical Server \"%1\" not found" The named logical server was not found in the database.

Click here for a list of possible parameters and odbc states.

2546 Error 0A006 -1514L "Failed to checkout an IQ core license." Sysam License Manager was unable to obtain a valid IQ_CORE license.

Click here for a list of possible parameters and odbc states.

2547 Error 0A005 -1513L "Sysam License Manager initialization failed." Sysam License Manager initialization failed.

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.


Created April 27, 2010. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com