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 |
|---|---|---|---|---|---|
| -869L | Error | 2519 | 08W64 | "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. |
| -870L | Error | 2520 | WC002 | "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. |
| -871L | Error | 2521 | WJ029 | "The database needs to be restarted for this Java related command" | Java support in the database requires a database restart after some Java related commands are performed, for example, some Java commands like ALTER DATABASE UPGRADE JAVA ON require a restart before one performs any Java related commands that load a Java class into the database. Click here for a list of possible parameters and odbc states. |
| -872L | Error | 2522 | WP014 | "%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. |
| -873L | Error | 2523 | WP013 | "%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. |
| -874L | Error | 2526 | WX001 | "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. |
| -875L | Error | 2527 | 42W73 | "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. |
| -876L | Error | 2528 | 08W65 | "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. |
| -877L | Error | 2534 | 42W09 | "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. |
| -878L | Error | 2535 | 42W74 | "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. |
| -879L | Error | 2536 | WC003 | "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. |
| -881L | Error | 2540 | WC005 | "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. |
| -883L | Error | 2544 | WC007 | "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. |
| -887L | Error | 2548 | 54W50 | "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. |
| -888L | Error | 2550 | WX002 | "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. |
| -889L | Error | 2551 | 42W79 | "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. |
| -890L | Error | 2553 | 54W01 | "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. |
| -891L | Error | 2554 | WC008 | "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. |
| -892L | Error | 2555 | WX003 | "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. |
| -893L | Error | 2556 | WX004 | "Illegal flags value passed to OPENXML" | The flags value passed to OPENXML as the third argument must be either 1 (attribute-centric mapping), or 2 (element-centric mapping). Click here for a list of possible parameters and odbc states. |