Messages on this page are sorted by SQLSTATE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL State | Msg Type | Number | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| WW231 | Error | 2966 | -1279L | "Operation '%1' failed for reason: '%2'" | The requested operation failed. Click here for a list of possible parameters and odbc states. |
| WW232 | Error | 2967 | -1280L | "Underflow when converting '%1'" | An underflow occurred when converting the specified type. The source type may be too small (for example zero length binary) or value may be too small to be represented by the destination type. Click here for a list of possible parameters and odbc states. |
| WW233 | Error | 2971 | -1284L | "Invalid partition key specification: must use '%1'. " | Partition key cannot be changed for ALTER TABLE ADD PARTITION. It must specify the same partition key column as the CREATE TABLE did. Click here for a list of possible parameters and odbc states. |
| WW234 | Warning | 2972 | 149L | "Automatic database upgrade applied" | The database is from an older version of the software. Automatic database upgrade occurs during startup. Subsequently the database can no longer be opened with the older version of the software. Click here for a list of possible parameters and odbc states. |
| WW235 | Error | 2979 | -1291L | "Column '%1' Partition '%2' may not be assigned to a dbspace because partitioning is not supported for datatype '%3'." | The column storage for certain datatypes (e.g., BIT datatype) cannot be assigned to a dbspace. Click here for a list of possible parameters and odbc states. |
| WW236 | Error | 2980 | -1292L | "Column '%1' may not be assigned to a dbspace because partitioning is not supported for datatype '%2'." | The column storage for certain datatypes (e.g., BIT datatype) cannot be assigned to a dbspace. Click here for a list of possible parameters and odbc states. |
| WW237 | Error | 2981 | -1293L | "Partition key of '%1' is unsupported." | Partitioning over the specified datatype is not supported. Click here for a list of possible parameters and odbc states. |
| WW238 | Error | 2994 | -1306L | "IN DBSPACE clause cannot be used for column '%1' since table '%2' is a partitioned table." | Entire column cannot be assigned to a dbspace using the IN DBSPACE clause, if the table is a partitioned table. Click here for a list of possible parameters and odbc states. |
| WX001 | Error | 2526 | -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. |
| WX002 | Error | 2550 | -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. |
| WX003 | Error | 2555 | -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. |
| WX004 | Error | 2556 | -893L | "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. |
| WX005 | Error | 2563 | -897L | "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. |
| WX006 | Error | 2564 | -898L | "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. |
| WX007 | Error | 2565 | -899L | "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. |
| WX008 | Error | 2566 | -900L | "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. |
| WX009 | Error | 2567 | -901L | "Undeclared tag ID: '%1'" | Every value appearing in the Tag column of the table must be declared in the TagNumber field of at least one column name. Click here for a list of possible parameters and odbc states. |
| WX010 | Error | 2568 | -902L | "Too few columns" | FOR XML EXPLICIT requires at least three columns: the tag column, the parent column, and one or more data columns. Click here for a list of possible parameters and odbc states. |
| WX011 | Error | 2569 | -903L | "CDATA has a name" | A CDATA directive in a FOR XML EXPLICIT query must not be given a name. Click here for a list of possible parameters and odbc states. |
| WX012 | Error | 2571 | -905L | "Invalid XQuery constructor" | The XQuery constructor passed as the first argument to XMLGEN was not valid. Click here for a list of possible parameters and odbc states. |