Table 52 lists and describes the SQLSTATE values that the XML
Extender returns. The description of each SQLSTATE value includes its
symbolic representation. The table also lists the message number that
is associated with each SQLSTATE value. See Messages for information about each message.
Table 52. SQLSTATE codes and associated message numbers
SQLSTATE | Message No. | Description |
---|---|---|
00000 | DXXnnnnI | No error has occurred. |
01HX0 | DXXD003W | The element or attribute specified in the path expression is missing from the XML document. |
38X00 | DXXC000E | The XML Extender is unable to open the specified file. |
38X01 | DXXA072E | XML Extender tried to automatically bind the database before enabling it, but could not find the bind files |
| DXXC001E | The XML Extender could not find the file specified. |
38X02 | DXXC002E | The XML Extender is unable to read data from the specified file. |
38X03 | DXXC003E | The XML Extender is unable to write data to the file. |
| DXXC011E | The XML Extender is unable to write data to the trace control file. |
38X04 | DXXC004E | The XML Extender was unable to operate the specified locator. |
38X05 | DXXC005E | The file size is greater than the XMLVarchar size and the XML Extender is unable to import all the data from the file. |
38X06 | DXXC006E | The file size is greater than the size of the XMLCLOB and the XML Extender is unable to import all the data from the file. |
38X07 | DXXC007E | The number of bytes in the LOB Locator does not equal the file size. |
38X08 | DXXD001E | A scalar extraction function used a location path that occurs multiple times. A scalar function can only use a location path that does not have multiple occurence. |
38X09 | DXXD002E | The path expression is syntactically incorrect. |
38X10 | DXXG002E | The XML Extender was unable to allocate memory from the operating system. |
38X11 | DXXA009E | This stored procedure is for XML Column only. |
38X12 | DXXA010E | While attempting to enable the column, the XML Extender could not find the DTD ID, which is the identifier specified for the DTD in the document access definition (DAD) file. |
38X14 | DXXD000E | There was an attempt to store an invalid document into a table. Validation has failed. |
38X15 | DXXA056E | The validation element in document access definition (DAD) file is wrong or missing. |
| DXXA057E | The name attribute of a side table in the document access definition (DAD) file is wrong or missing. |
| DXXA058E | The name attribute of a column in the document access definition (DAD) file is wrong or missing. |
| DXXA059E | The type attribute of a column in the document access definition (DAD) file is wrong or missing. |
| DXXA060E | The path attribute of a column in the document access definition (DAD) file is wrong or missing. |
| DXXA061E | The multi_occurrence attribute of a column in the document access definition (DAD) file is wrong or missing. |
| DXXQ000E | A mandatory element is missing from the document access definition (DAD) file. |
38X16 | DXXG004E | A null value for a required parameter was passed to an XML stored procedure. |
38X17 | DXXQ001E | The SQL statment in the document access definition (DAD) or the one that overrides it is not valid. A SELECT statement is required for generating XML documents. |
38X18 | DXXG001E | XML Extender encountered an internal error. |
| DXXG006E | XML Extender encountered an internal error while using CLI. |
38X19 | DXXQ002E | The system is running out of space in memory or disk. There is no space to contain the resulting XML documents. |
38X20 | DXXQ003W | The user-defined SQL query generates more XML documents than the specified maximum. Only the specified number of documents are returned. |
38X21 | DXXQ004E | The specified column is not one of the columns in the result of the SQL query. |
38X22 | DXXQ005E | The mapping of the SQL query to XML is incorrect. |
38X23 | DXXQ006E | An attribute_node element in the document access definition(DAD) file does not have a name attribute. |
38X24 | DXXQ007E | The attribute_node element in the document access definition (DAD) does not have a column element or RDB_node. |
38X25 | DXXQ008E | A text_node element in the document access definition (DAD) file does not have a column element. |
38X26 | DXXQ009E | The specified result table could not be found in the system catalog. |
38X27 | DXXQ010E | The RDB_node of the attribute_node or text_node must have a table. |
| DXXQ011E | The RDB_node of the attribute_node or text_node must have a column. |
| DXXQ017E | An XML document generated by the XML Extender is too large to fit into the column of the result table. |
38X28 | DXXQ012E | XML Extender could not find the expected element while processing the DAD. |
| DXXQ016E | All tables must be defined in the RDB_node of the top element in the document access definition (DAD) file. Sub-element tables must match the tables defined in the top element. The table name in this RDB_node is not in the top element. |
38X29 | DXXQ013E | The element table or column must have a name in the document access definition (DAD) file. |
| DXXQ015E | The condition in the condition element in the document access definition (DAD) has an invalid format. |
38X30 | DXXQ014E | An element_node element in the document access definition (DAD) file does not have a name attribute. |
| DXXQ018E | The ORDER BY clause is missing from the SQL statement in a document access definition (DAD) file that maps SQL to XML. |
38X31 | DXXQ019E | The objids element does not have a column element in the document access definition (DAD) file that maps SQL to XML. |
38X36 | DXXA073E | The database was not bound when user tried to enable it. |
38X37 | DXXG007E | The server operating system locale is inconsistent with DB2 code page. |
38X38 | DXXG008E | The server operating system locale can not be found in the code page table. |
38x33 | DXXG005E | This parameter is not supported in this release, will be supported in the future release. |
38x34 | DXXG000E | An invalid file name was specified. |