The XML Extender generates the following messages when it completes an operation or detects an error.
DXXA000I | Enabling column <column_name>. Please Wait. |
Explanation: This is an informational messages.
User Response: No action required.
DXXA001S | An unexpected error occurred in build <build_ID>, file <file_name>, and line <line_number>. |
Explanation: An unexpected error occurred.
User Response: If this error persists, contact your Software Service Provider. When reporting the error, be sure to include all the message text, the trace file, and an explanation of how to reproduce the problem.
DXXA002I | Connecting to database <database>. |
Explanation: This is an informational message.
User Response: No action required.
DXXA003E | Cannot connect to database <database>. |
Explanation: The database specified might not exist or could be corrupted.
User Response:
DXXA004E | Cannot enable database <database>. |
Explanation: The database might already be enabled or might be corrupted.
User Response:
DXXA005I | Enabling database <database>. Please wait. |
Explanation: This is an informational message.
User Response: No action required.
DXXA006I | The database <database> was enabled successfully. |
Explanation: This is an informational message.
User Response: No action required.
DXXA007E | Cannot disable database <database>. |
Explanation: The database cannot be disabled by XML Extender if it contains any XML columns or collections.
User Response: Backup any important data, disable any XML columns or collections, and update or drop any tables until there are no XML data types left in the database.
DXXA008I | Disabling column <column_name>. Please Wait. |
Explanation: This is an information message.
User Response: No action required.
DXXA009E | Xcolumn tag is not specified in the DAD file. |
Explanation: This stored procedure is for XML Column only.
User Response: Ensure the Xcolumn tag is specified correctly in the DAD file.
DXXA010E | Attempt to find DTD ID <dtdid> failed. |
Explanation: 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.
User Response: Ensure the correct value for the DTD ID is specified in the DAD file.
DXXA011E | Inserting a record into DB2XML.XML_USAGE table failed. |
Explanation: While attempting to enable the column, the XML Extender could not insert a record into the DB2XML.XML_USAGE table.
User Response: Ensure the DB2XML.XML_USAGE table exists and that a record by the same name does not already exist in the table.
DXXA012E | Attempt to update DB2XML.DTD_REF table failed. |
Explanation: While attempting to enable the column, the XML Extender could not update the DB2XML.DTD_REF table.
User Response: Ensure the DB2XML.DTD_REF table exists. Determine whether the table is corrupted or if the administration user ID has the correct authority to update the table.
DXXA013E | Attempt to alter table <table_name> failed. |
Explanation: While attempting to enable the column, the XML Extender could not alter the specified table.
User Response: Check the privileges required to alter the table.
DXXA014E | The specified root ID column: <root_id> is not a single primary key of table <table_name>. |
Explanation: The root ID specified is either not a key, or it is not a single key of table table_name.
User Response: Ensure the specified root ID is the single primary key of the table.
DXXA015E | The column DXXROOT_ID already exists in table <table_name>. |
Explanation: The column DXXROOT_ID exists, but was not created by XML Extender.
User Response: Specify a primary column for the root ID option when enabling a column, using a different different column name.
DXXA016E | The input table <table_name> does not exist. |
Explanation: The XML Extender was unable to find the specified table in the system catalog.
User Response: Ensure that the table exists in the database, and is specified correctly.
DXXA017E | The input column <column_name> does not exist in the specified table <table_name>. |
Explanation: The XML Extender was unable to find the column in the system catalog.
User Response: Ensure the column exists in a user table.
DXXA018E | The specified column is not enabled for XML data. |
Explanation: While attempting to disable the column, XML Extender could not find the column in the DB2XML.XML_USAGE table, indicating that the column is not enabled. If the column is not XML-enabled, you do not need to disable it.
User Response: No action required.
DXXA019E | A input parameter required to enable the column is null. |
Explanation: A required input parameter for the enable_column() stored procedure is null.
User Response: Check all the input parameters for the enable_column() stored procedure.
DXXA020E | Columns cannot be found in the table <table_name>. |
Explanation: While attempting to create the default view, the XML Extender could not find columns in the specified table.
User Response: Ensure the column and table name are specified correctly.
DXXA021E | Cannot create the default view <default_view>. |
Explanation: While attempting to enable a column, the XML Extender could not create the specified view.
User Response: Ensure that the default view name is unique. If a view with the name already exists, specify a unique name for the default view.
DXXA022I | Column <column_name> enabled. |
Explanation: This is an informational message.
User Response: No response required.
DXXA023E | Cannot find the DAD file. |
Explanation: While attempting to disable a column, the XML Extender was unable to find the document access definition (DAD) file.
User Response: Ensure you specified the correct database name, table name, or column name.
DXXA024E | The XML Extender encountered an internal error while accessing the system catalog tables. |
Explanation: The XML Extender was unable to access system catalog table.
User Response: Ensure the database is in a stable state.
DXXA025E | Cannot drop the default view <default_view>. |
Explanation: While attempting to disable a column, the XML Extender could not drop the default view.
User Response: Ensure the administration user ID for XML Extender has the privileges necessary to drop the default view.
DXXA026E | Unable to drop the side table <side_table>. |
Explanation: While attempting to disable a column, the XML Extender was unable to drop the specified table.
User Response: Ensure that the administrator user ID for XML Extender has the privileges necessary to drop the table.
DXXA027E | Could not disable the column. |
Explanation: XML Extender could not disable a column because an internal trigger failed. Possible causes:
User Response: Use the trace facility to create a trace file and try to correct the problem. If the problem persists, contact your Software Service Provider and provide the trace file.
DXXA028E | Could not disable the column. |
Explanation: XML Extender could not disable a column because an internal trigger failed. Possible causes:
User Response: Use the trace facility to create a trace file and try to correct the problem. If the problem persists, contact your Software Service Provider and provide the trace file.
DXXA029E | Could not disable the column. |
Explanation: XML Extender could not disable a column because an internal trigger failed. Possible causes:
User Response: Use the trace facility to create a trace file and try to correct the problem. If the problem persists, contact your Software Service Provider and provide the trace file.
DXXA030E | Could not disable the column. |
Explanation: XML Extender could not disable a column because an internal trigger failed. Possible causes:
User Response: Use the trace facility to create a trace file and try to correct the problem. If the problem persists, contact your Software Service Provider and provide the trace file.
DXXA031E | Unable to reset the DXXROOT_ID column value in the application table to NULL. |
Explanation: While attempting to disable a column, the XML Extender was unable to set the value of DXXROOT_ID in the application table to NULL.
User Response: Ensure that the administrator user ID for XML Extender has the privileges necessary to alter the application table.
DXXA032E | Decrement of USAGE_COUNT in DB2XML.XML_USAGE table failed. |
Explanation: While attempting to disable the column, the XML Extender was unable to reduce the value of the USAGE_COUNT column by one.
User Response: Ensure that the DB2XML.XML_USAGE table exists and that the administrator user ID for XML Extender has the necessary privileges to update the table.
DXXA033E | Attempt to delete a row from the DB2XML.XML_USAGE table failed. |
Explanation: While attempting to disable a column, the XML Extender was unable to delete its associate row in the DB2XML.XML_USAGE table.
User Response: Ensure that the DB2XML.XML_USAGE table exists and that the administration user ID for XML Extender has the privileges necessary to update this table.
DXXA034I | XML Extender has successfully disabled column <column_name>. |
Explanation: This is an informational message
User Response: No action required.
DXXA035I | XML Extender is disabling database <database>. Please wait. |
Explanation: This is an informational message.
User Response: No action is required.
DXXA036I | XML Extender has successfully disabled database <database>. |
Explanation: This is an informational message.
User Response: No action is required.
DXXA037E | The specified table space name is longer than 18 characters. |
Explanation: The table space name cannot be longer than 18 alphanumeric characters.
User Response: Specify a name less than 18 characters.
DXXA038E | The specified default view name is longer than 18 characters. |
Explanation: The default view name cannot be longer than 18 alphanumeric characters.
User Response: Specify a name less than 18 characters.
DXXA039E | The specified ROOT_ID name is longer than 18 characters. |
Explanation: The ROOT_ID name cannot be longer than 18 alphanumeric characters.
User Response: Specify a name less than 18 characters.
DXXA046E | Unable to create the side table <side_table>. |
Explanation: While attempting to enable a column, the XML Extender was unable to create the specified side table.
User Response: Ensure that the administrator user ID for XML Extender has the privileges necessary to create the side table.
DXXA047E | Could not enable the column. |
Explanation: XML Extender could not enable a column because an internal trigger failed. Possible causes:
User Response: Use the trace facility to create a trace file and try to correct the problem. If the problem persists, contact your Software Service Provider and provide the trace file.
DXXA048E | Could not enable the column. |
Explanation: XML Extender could not enable a column because an internal trigger failed. Possible causes:
User Response: Use the trace facility to create a trace file and try to correct the problem. If the problem persists, contact your Software Service Provider and provide the trace file.
DXXA049E | Could not enable the column. |
Explanation: XML Extender could not enable a column because an internal trigger failed. Possible causes:
User Response: Use the trace facility to create a trace file and try to correct the problem. If the problem persists, contact your Software Service Provider and provide the trace file.
DXXA050E | Could not enable the column. |
Explanation: XML Extender could not enable a column because an internal trigger failed. Possible causes:
User Response: Use the trace facility to create a trace file and try to correct the problem. If the problem persists, contact your Software Service Provider and provide the trace file.
DXXA051E | Could not disable the column. |
Explanation: XML Extender could not disable a column because an internal trigger failed. Possible causes:
User Response: Use the trace facility to create a trace file and try to correct the problem. If the problem persists, contact your Software Service Provider and provide the trace file.
DXXA052E | Could not disable the column. |
Explanation: XML Extender could not disable a column because an internal trigger failed. Possible causes:
User Response: Use the trace facility to create a trace file and try to correct the problem. If the problem persists, contact your Software Service Provider and provide the trace file.
DXXA053E | Could not enable the column. |
Explanation: XML Extender could not enable a column because an internal trigger failed. Possible causes:
User Response: Use the trace facility to create a trace file and try to correct the problem. If the problem persists, contact your Software Service Provider and provide the trace file.
DXXA054E | Could not enable the column. |
Explanation: XML Extender could not enable a column because an internal trigger failed. Possible causes:
User Response: Use the trace facility to create a trace file and try to correct the problem. If the problem persists, contact your Software Service Provider and provide the trace file.
DXXA056E | The validation value <validation_value> in the DAD file is invalid. |
Explanation: The validation element in document access definition (DAD) file is wrong or missing.
User Response: Ensure that the validation element is specified correctly in the DAD file.
DXXA057E | A side table name <side_table_name> in DAD is invalid. |
Explanation: The name attribute of a side table in the document access definition (DAD) file is wrong or missing.
User Response: Ensure that the name attribute of a side table is specified correctly in the DAD file.
DXXA058E | A column name <column_name> in the DAD file is invalid. |
Explanation: The name attribute of a column in the document access definition (DAD) file is wrong or missing.
User Response: Ensure that the name attribute of a column is specified correctly in the DAD file.
DXXA059E | The type <column_type> of column <column_name> in the DAD file is invalid. |
Explanation: The type attribute of a column in the document access definition (DAD) file is wrong or missing.
User Response: Ensure that the type attribute of a column is specified correctly in the DAD file.
DXXA060E | The path attribute <location_path> of <column_name> in the DAD file is invalid. |
Explanation: The path attribute of a column in the document access definition (DAD) file is wrong or missing.
User Response: Ensure that the path attribute of a column is specified correctly in the DAD file.
DXXA061E | The multi_occurrence attribute <multi_occurrence> of <column_name> in the DAD file is invalid. |
Explanation: The multi_occurrence attribute of a column in the document access definition (DAD) file is wrong or missing.
User Response: Ensure that the multi_occurrence attribute of a column is specified correctly in the DAD file.
DXXA062E | Unable to retrieve the column number for <column_name> in table <table_name>. |
Explanation: XML Extender could not retrieve the column number for column_name in table table_name from the system catalog.
User Response: Make sure the application table is well defined.
DXXA063I | Enabling collection <collection_name>. Please Wait. |
Explanation: This is an information message.
User Response: No action required.
DXXA064I | Disabling collection <collection_name>. Please Wait. |
Explanation: This is an information message.
User Response: No action required.
DXXA065E | Calling stored procedure <procedure_name> failed. |
Explanation: Check the shared library db2xml and see if the permission is correct.
User Response: Make sure the client has permission to run the stored procedure.
DXXA066I | XML Extender has successfully disabled collection <collection_name>. |
Explanation: This is an informational message.
User Response: No response required.
DXXA067I | XML Extender has successfully enabled collection <collection_name>. |
Explanation: This is an informational message.
User Response: No response required.
DXXA068I | XML Extender has successfully turned the trace on. |
Explanation: This is an informational message.
User Response: No response required.
DXXA069I | XML Extender has successfully turned the trace off. |
Explanation: This is an informational message.
User Response: No response required.
DXXA070W | The database has already been enabled. |
Explanation: The enable database command was executed on the enabled database
User Response: No action is required.
DXXA071W | The database has already been disabled. |
Explanation: The disable database command was executed on the disabled database
User Response: No action is required.
DXXA072E | XML Extender couldn't find the bind files. Bind the database before enabling it. |
Explanation: XML Extender tried to automatically bind the database before enabling it, but could not find the bind files
User Response: Bind the database before enabling it.
DXXA073E | The database is not bound. Please bind the database before enabling it. |
Explanation: The database was not bound when user tried to enable it.
User Response: Bind the database before enabling it.
DXXA074E | Wrong parameter type. The stored procedure expects a STRING parameter. |
Explanation: The stored procedure expects a STRING parameter.
User Response: Declare the input parameter to be STRING type.
DXXA075E | Wrong parameter type. The input parameter should be a LONG type. |
Explanation: The stored procedure expects the input parameter to be a LONG type.
User Response: Declare the input parameter to be a LONG type.
DXXA076E | XML Extender trace instance ID invalid. |
Explanation: Cannot start trace with the instance ID provided.
User Response: Ensure that the instance ID is a valid AS/400 user ID.
DXXC000E | Unable to open the specified file. |
Explanation: The XML Extender is unable to open the specified file.
User Response: Ensure that the application user ID has read and write permission for the file.
DXXC001E | The specified file is not found. |
Explanation: The XML Extender could not find the file specified.
User Response: Ensure that the file exists and the path is specified correctly.
DXXC002E | Unable to read file. |
Explanation: The XML Extender is unable to read data from the specified file.
User Response: Ensure that the application user ID has read permission for the file.
DXXC003E | Unable to write to the specified file. |
Explanation: The XML Extender is unable to write data to the file.
User Response: Ensure that the application user ID has write permission for the file or that the file system has sufficient space.
DXXC004E | Unable to operate the LOB Locator: rc=<locator_rc>. |
Explanation: The XML Extender was unable to operate the specified locator.
User Response: Ensure the LOB Locator is set correctly.
DXXC005E | Input file size is greater than XMLVarchar size. |
Explanation: The file size is greater than the XMLVarchar size and the XML Extender is unable to import all the data from the file.
User Response: Use the XMLCLOB column type.
DXXC006E | The input file exceeds the DB2 LOB limit. |
Explanation: 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.
User Response: Decompose the file into smaller objects or use an XML collection.
DXXC007E | Unable to retrieve data from the file to the LOB Locator. |
Explanation: The number of bytes in the LOB Locator does not equal the file size.
User Response: Ensure the LOB Locator is set correctly.
DXXC008E | Can not remove the file <file_name>. |
Explanation: The file has a sharing access violation or is still open.
User Response: Close the file or stop any processes that are holding the file. You might have to stop and restart DB2.
DXXC009E | Unable to create file to <directory> directory. |
Explanation: The XML Extender is unable to create a file in directory directory.
User Response: Ensure that the directory exists, that the application user ID has write permission for the directory, and that the file system has sufficient space for the file.
DXXC010E | Error while writing to file <file_name>. |
Explanation: There was an error while writing to the file file_name.
User Response: Ensure that the file system has sufficient space for the file.
DXXC011E | Unable to write to the trace control file. |
Explanation: The XML Extender is unable to write data to the trace control file.
User Response: Ensure that the application user ID has write permission for the file or that the file system has sufficient space.
DXXC012E | Cannot create temporary file. |
Explanation: Cannot create file in system temp directory.
User Response: Ensure that the application user ID has write permission for the file system temp directory or that the file system has sufficient space for the file.
DXXD000E | An invalid XML document is rejected. |
Explanation: There was an attempt to store an invalid document into a table. Validation has failed.
User Response: Check the document with its DTD using an editor that can view invisible invalid characters. To suppress this error, turn off validation in the DAD file.
DXXD001E | <location_path> occurs multiple times. |
Explanation: 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.
User Response: Use a table function (add an 's' to the end of the scalar function name).
DXXD002E | A syntax error occurred near position <position> in the search path. |
Explanation: The path expression is syntactically incorrect.
User Response: Correct the search path argument of the query. Refer to the documentation for the syntax of path expressions.
DXXD003W | Path not found. Null is returned. |
Explanation: The element or attribute specified in the path expression is missing from the XML document.
User Response: Verify that the specified path is correct.
DXXG000E | The file name <file_name> is invalid. |
Explanation: An invalid file name was specified.
User Response: Specify a correct file name and try again.
DXXG001E | An internal error occured in build <build_ID>, file <file_name>, and line <line_number>. |
Explanation: XML Extender encountered an internal error.
User Response: Contact your Software Service Provider. When reporting the error, be sure to include all the messages, the trace file and how to reproduce the error.
DXXG002E | The system is out of memory. |
Explanation: The XML Extender was unable to allocate memory from the operating system.
User Response: Close some applications and try again. If the problem persists, refer to your operating system documentation for assistance. Some operating systems might require that you reboot the system to correct the problem.
DXXG004E | Invalid null parameter. |
Explanation: A null value for a required parameter was passed to an XML stored procedure.
User Response: Check all required parameters in the argument list for the stored procedure call.
DXXG005E | Parameter not supported. |
Explanation: This parameter is not supported in this release, will be supported in the future release.
User Response: Set this parameter to NULL.
DXXG006E | Internal Error CLISTATE=<clistate>, RC=<cli_rc>, build <build_ID>, file <file_name>, line <line_number> CLIMSG=<CLI_msg>. |
Explanation: XML Extender encountered an internal error while using CLI.
User Response: Contact your Software Service Provider. Potentially this error can be caused by incorrect user input. When reporting the error, be sure to include all output messages, trace log, and how to reproduce the problem. Where possible, send any DADs, XML documents, and table definitions which apply.
DXXG007E | Locale <locale> is inconsistent with DB2 code page <code_page>. |
Explanation: The server operating system locale is inconsistent with DB2 code page.
User Response: Correct the server operating system locale and restart DB2.
DXXG008E | Locale <locale> is not supported. |
Explanation: The server operating system locale can not be found in the code page table.
User Response: Correct the server operating system locale and restart DB2.
DXXQ000E | <Element> is missing from the DAD file. |
Explanation: A mandatory element is missing from the document access definition (DAD) file.
User Response: Add the missing element to the DAD file.
DXXQ001E | Invalid SQL statment for XML generation. |
Explanation: 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.
User Response: Correct the SQL statment.
DXXQ002E | Cannot generate storage space to hold XML documents. |
Explanation: The system is running out of space in memory or disk. There is no space to contain the resulting XML documents.
User Response: Limit the number of documents to be generated. Reduce the size of each documents by removing some unnecessary element and attribute nodes from the document access definition (DAD) file.
DXXQ003W | Result exceeds maximum. |
Explanation: The user-defined SQL query generates more XML documents than the specified maximum. Only the specified number of documents are returned.
User Response: No action is required. If all documents are needed, specify zero as the maximum number of documents.
DXXQ004E | The column <column_name> is not in the result of the query. |
Explanation: The specified column is not one of the columns in the result of the SQL query.
User Response: Change the specified column name in the document access definition (DAD) file to make it one of the columns in the result of the SQL query. Alternatively, change the SQL query so that it has the specified column in its result.
DXXQ004W | The DTD ID was not found in the DAD. |
Explanation: In the DAD, VALIDATION is YES but the DTDID element is not specified. NO validation check is performed.
User Response: No action is required. If validation is needed, specify the DTDID element in the DAD file.
DXXQ005E | Wrong relational mapping. The element <element_name> is at a lower level than its child column <column_name>. |
Explanation: The mapping of the SQL query to XML is incorrect.
User Response: Make sure that the columns in the result of the SQL query are in a top-down order of the relational hierarchy. Also make sure that there is a single-column candidate key to begin each level. If such a key is not available in a table, the query should generate one for that table using a table expression and the DB2 built-in function generate_unique().
DXXQ006E | An attribute_node element has no name. |
Explanation: An attribute_node element in the document access definition(DAD) file does not have a name attribute.
User Response: Ensure that every attribute_node has a name in the DAD file.
DXXQ007E | The attribute_node <attribute_name> has no column element or RDB_node. |
Explanation: The attribute_node element in the document access definition (DAD) does not have a column element or RDB_node.
User Response: Ensure that every attribute_node has a column element or RDB_node in the DAD.
DXXQ008E | A text_node element has no column element. |
Explanation: A text_node element in the document access definition (DAD) file does not have a column element.
User Response: Ensure that every text_node has a column element in the DAD.
DXXQ009E | Result table <table_name> does not exist. |
Explanation: The specified result table could not be found in the system catalog.
User Response: Create the result table before calling the stored procedure.
DXXQ010E | RDB_node of <node_name> does not have a table in the DAD file. |
Explanation: The RDB_node of the attribute_node or text_node must have a table.
User Response: Specify the table of RDB_node for attribute_node or text_node in the document access definition (DAD) file.
DXXQ011E | RDB_node element of <node_name> does not have a column in the DAD file. |
Explanation: The RDB_node of the attribute_node or text_node must have a column.
User Response: Specify the column of RDB_node for attribute_node or text_node in the document access definition (DAD) file.
DXXQ012E | Errors occurred in DAD. |
Explanation: XML Extender could not find the expected element while processing the DAD.
User Response: Check that the DAD is a valid XML document and contains all the elements required by the DAD DTD. Consult the XML Extender publication for the DAD DTD.
DXXQ013E | The table or column element does not have a name in the DAD file. |
Explanation: The element table or column must have a name in the document access definition (DAD) file.
User Response: Specify the name of table or column element in the DAD.
DXXQ014E | An element_node element has no name. |
Explanation: An element_node element in the document access definition (DAD) file does not have a name attribute.
User Response: Ensure that every element_node element has a name in the DAD file.
DXXQ015E | The condition format is invalid. |
Explanation: The condition in the condition element in the document access definition (DAD) has an invalid format.
User Response: Ensure that the format of the condition is valid.
DXXQ016E | The table name in this RDB_node is not defined in the top element of the DAD file. |
Explanation: 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.
User Response: Ensure that the table of the RDB node is defined in the top element of the DAD file.
DXXQ017E | The column in the result table <table_name> is too small. |
Explanation: An XML document generated by the XML Extender is too large to fit into the column of the result table.
User Response: Drop the result table. Create another result table with a bigger column. Rerun the stored procedure.
DXXQ018E | The ORDER BY clause is missing from the SQL statement. |
Explanation: The ORDER BY clause is missing from the SQL statement in a document access definition (DAD) file that maps SQL to XML.
User Response: Edit the DAD file. Add an ORDER BY clause that contains the entity-identifying columns.
DXXQ019E | The element objids has no column element in the DAD file. |
Explanation: The objids element does not have a column element in the document access definition (DAD) file that maps SQL to XML.
User Response: Edit the DAD file. Add the key columns as sub-elements of the element objids.
DXXQ020I | XML successfully generated. |
Explanation: The requested XML documents have been successfully generated from the database.
User Response: No action is required.
DXXQ021E | Table <table_name> does not have column <column_name>. |
Explanation: The table does not have the specified column in the database.
User Response: Specify another column name in DAD or add the specified column into the table database.
DXXQ022E | Column <column_name> of <table_name> should have type <type_name>. |
Explanation: The type of the column is wrong.
User Response: Correct the type of the column in the document access definition (DAD).
DXXQ023E | Column <column_name> of <table_name> cannot be longer than <length>. |
Explanation: The length defined for the column in the DAD is too long.
User Response: Correct the column length in the document access definition (DAD).
DXXQ024E | Can not create table <table_name>. |
Explanation: The specified table can not be created.
User Response: Ensure that the user ID creating the table has the necessary authority to create a table in the database.
DXXQ025I | XML decomposed successfully. |
Explanation: An XML document has been decomposed and stored in a collection successfully.
User Response: No action is required.
DXXQ026E | XML data <xml_name> is too large to fit in column <column_name>. |
Explanation: The specified piece of data from an XML document is too large to fit into the specified column.
User Response: Increase the length of the column using the ALTER TABLE statement or reduce the size of the data by editing the XML document.
DXXQ028E | Cannot find the collection <collection_name> in the XML_USAGE table. |
Explanation: A record for the collection cannot be found in the XML_USAGE table.
User Response: Verify that you have enabled the collection.
DXXQ029E | Cannot find the DAD in XML_USAGE table for the collection <collection_name>. |
Explanation: A DAD record for the collection cannot be found in the XML_USAGE table.
User Response: Ensure that you have enabled the collection correctly.
DXXQ030E | Wrong XML override syntax. |
Explanation: The XML_override value is specified incorrectly in the stored procedure.
User Response: Ensure that the syntax of XML_override is correct.
DXXQ031E | Table name cannot be longer than maximum length allowed by DB2. |
Explanation: The table name specified by the condition element in the DAD is too long.
User Response: Correct the length of the table name in document access definition (DAD).
DXXQ032E | Column name cannot be longer than maximum length allowed by DB2. |
Explanation: The column name specified by the condition element in the DAD is too long.
User Response: Correct the length of the column name in the document access definition (DAD).
DXXQ033E | Invalid identifier starting at <identifier> |
Explanation: The string is not a valid DB2 SQL identifier.
User Response: Correct the string in the DAD to conform to the rules for DB2 SQL identifiers.
DXXQ034E | Invalid condition element in top RDB_node of DAD: <condition> |
Explanation: The condition element must be a valid WHERE clause consisting of join conditions connected by the conjunction AND.
User Response: See the XML Extender documentation for the correct syntax of the join condition in a DAD.
DXXQ035E | Invalid join condition in top RDB_node of DAD: <condition> |
Explanation: Column names in the condition element of the top RDB_node must be qualified with the table name if the DAD specifies multiple tables.
User Response: See the XML Extender documentation for the correct syntax of the join condition in a DAD.
DXXQ036E | A Schema name specified under a DAD condition tag is longer than allowed. |
Explanation: An error was detected while parsing text under a condition tag within the DAD. The condition text contains an id qualified by a schema name that is too long.
User Response: Correct the text of the condition tags in document access definition (DAD).
DXXQ037E | Cannot generate <element> with multiple occurrences. |
Explanation: The element node and its descandents have no mapping to database, but its multi_occurrence equals YES.
User Response: Correct the DAD by either setting the multi_occurrence to NO or create a RDB_node in one of its descandents.