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 |
|---|---|---|---|---|---|
| -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' 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. |
| -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. |
| -894L | Error | 2557 | 0AW14 | "Plan cannot be generated for this type of statement" | You tried to get the execution plan for a statement type that is not supported. Click here for a list of possible parameters and odbc states. |
| -895L | Error | 2558 | 08W66 | "Encryption error: %1" | An error occurred during encryption. Click here for a list of possible parameters and odbc states. |
| -896L | Error | 2560 | 42W82 | "Cannot delete PUBLIC option '%1' since user settings exist" | You tried to delete a PUBLIC option, but there are user settings for the same option. The user settings must be deleted before the PUBLIC option is deleted. Click here for a list of possible parameters and odbc states. |
| -897L | Error | 2563 | WX005 | "Illegal FOR XML EXPLICIT tag value: '%1'" | FOR XML EXPLICIT tag values must be greater than 0 and less than 256. Also, NULL values are not allowed in the Tag column. Click here for a list of possible parameters and odbc states. |
| -898L | Error | 2564 | WX006 | "Unknown FOR XML EXPLICIT directive: '%1'" | Legal FOR XML EXPLICIT directives are: id, idref, idrefs, hide, element, xml, cdata. Click here for a list of possible parameters and odbc states. |
| -899L | Error | 2565 | WX007 | "Illegal column name: '%1'" | FOR XML EXPLICIT column names can consist of up to four fields separated by exclamation marks. The first two columns must be named Tag and Parent. Click here for a list of possible parameters and odbc states. |
| -900L | Error | 2566 | WX008 | "Parent not open: '%1'" | FOR XML EXPLICIT requires the parent tag for a row to be opened when that row is read. Check the order of the rows returned by the query with the FOR XML EXPLICIT clause removed. Click here for a list of possible parameters and odbc states. |