The override parameter's description for the following stored procedures has changed:
The update is as follows:
Parameter | Description | IN/OUT Parameter |
---|---|---|
override | Overrides the condition in the DAD file. The input value
is based on the overrideType.
|
IN |
Decomposition uses RDB_node mapping to specify how an XML document is decomposed into DB2 UDB tables by extracting the element and attribute values and storing them in table rows. The values from each XML document are stored in one or more DB2 UDB tables. Each table can have a maximum of 10240 rows decomposed from each document.
For example, if an XML document is decomposed into five tables, each of the five tables can have up to 10240 rows for that particular document. If the table has rows for multiple documents, it can have up to 10240 rows for each document.
Using multiple-occurring elements (elements with location paths that can occur more than once in the XML structure) affects the number of rows . For example, a document that contains an element <Part> that occurs 20 times, might be decomposed as 20 rows in a table. When using multiple occurring elements, consider that a maximum of 10240 rows can be decomposed into one table from a single document.
You do not need to drop and recreate the stored procedure dxxShredXML to decompose documents that are larger than 1 MB. To decompose documents that are larger than 1 MB, invoke the stored procedure dxxShredXML100MB, which can shred documents up to 100 MB. Although dxxShredXML100MB can handle large documents, you might need to increase other resources for the stored procedure to complete successfully. To invoke the stored procedure through the sample program dxxshrd, use the new flag "-large". For example:
dxxshrd -large mydb xxx.xml
If your version of DB2 Universal Database is earlier than Version 8 FixPak 6, you must run dxxMigv to migrate XML Extender to the current level to run the new stored procedure.
You must configure and enable MQ XML user-defined functions (UDFs) before you can use them.
Install the UDFs by following the procedure in the "Installing DB2 WebSphere MQ functions" topic, which is found either in the Information Center or the IBM DB2 Information Integrator Application Developer's Guide.
To configure and enable MQ XML UDFs with XML Extender:
db2 connect to <database>
db2 bind @dbxxbind.lst
db2 bind mqxml.bnd
db2 bind @db2cli.lst
DB2 XML Extender can place large documents in temporary files to avoid using a great amount of memory during processing. On systems with large amounts of physical memory, you can avoid moving documents to temporary files, reducing the amount of Input/Output activity. The environment variable DB2DXX_MIN_TMPFILE_SIZE instructs XML Extender to use memory buffers, instead of temporary files, for processing documents smaller than the specified value. The variable is applicable only on the server. If multiple physical nodes participate in a partitioned environment, the variable can be set differently on each node, accurately reflecting the amount of memory installed on each computer. If the environment variable is not set, documents larger than 128 KB will automatically be placed into temporary files during processing. Documents smaller than 128 KB will be processed in memory.
You can redefine the user-defined type (UDT) DB2XML.XMLVarchar up to 32 KB. To change the size of an XMLVarchar UDT, create the UDT before you enable the database for XML Extender.
For more information, see DB2 XML Extender Administration and Programming.
[ Top of page |Previous page | Next page | Contents ]