Common XML indexing issues
If you encounter issues when indexing XML data, one of the following problem scenarios may apply.
Problem determination for SQL20305N and SQL20306N error messages
These error messages are issued when XML node values cannot be indexed. The SQL20305N message is issued by INSERT and UPDATE statements and by the import and load utilities. The SQL20306N message is issued by CREATE INDEX statements issued against populated base tables.
The
messages will output a reason code for the error. Issue ?
SQL20305 or ? SQL20306 from the Command
Line Processor to look up the explanation and user response for the
corresponding reason code. A generated XQuery statement is output
to the db2diag log file to help you locate the
failing XML node values.
If SQL20305N is issued by the load utility, the generated XQuery statements to locate the failing node values are not written to a db2diag log file. To generate these XQuery statements, the import utility must be run on the failing rows that were not loaded.
If SQL20305N is issued by an INSERT or UPDATE statement, see "Troubleshooting SQL20305N messages issued by INSERT or UPDATE statements." If SQL20306N is issued by a CREATE INDEX statement, then see "Troubleshooting SQL20306N message issued by CREATE INDEX statements on populated tables."