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 |
|---|---|---|---|---|---|
| WX013 | Error | 2572 | -906L | "XMLGEN evaluation failure" | One of the variables referenced in the XQuery constructor was not found in the list of arguments. Click here for a list of possible parameters and odbc states. |
| WX014 | Error | 2573 | -907L | "No name for argument" | Unnamed arguments cannot be used as XML element or attribute names. Name unnamed items in the argument list using AS. Click here for a list of possible parameters and odbc states. |
| WX015 | Error | 2576 | -911L | "Control character in XML output" | A non-space character less than hex 20 was encountered while generating XML content. Consider base64 encoding strings that contain control characters before using them as XML content. This can be accomplished in a FOR XML query or SQLX function by casting the string to a type such as LONG BINARY. Click here for a list of possible parameters and odbc states. |
| WX016 | Error | 2577 | -912L | "Insufficient memory for OPENXML query" | The memory used by an OPENXML query may be proportional to the maximum distance between elements or attributes returned by a single row. For example, a query where some row uses the value from both the first and last element in the document may use memory proportional to the size of the document. One solution is to increase the cache size. Another is to break a query that refers to distant elements into several queries that refer to nearby elements and join the results. Click here for a list of possible parameters and odbc states. |