IncludeXML

Usage

Specify Yes to include data from XML columns in the changes to your target tables. Specify No when the source tables do not contain XML columns or when they contain XML columns, but you do not want to update the corresponding columns in the target tables.

Be aware of the following points about High-speed Apply Engine and XML processing:

• Valid logical log input files include XML column data in separate VSAM files (one set of VSAM files for each XML column, or each partition of each XML column). Ensure that the appropriate VSAM files are available to High-speed Apply Engine along with the logical log input file.

• If the Db2 subsystem of the target tables is different than the subsystem where your logical log input file was generated, ensure that an XMLSTRING control file:

  • Was generated along with your logical log input file
  • Is available to High-speed Apply Engine with the logical log input file

  The logical log XMLSTRING control file contains the string IDs and string data that Db2 uses to encode the data in XML columns. The product or program that generates the logical log must obtain this data from the Db2 catalog table SYSIBM.SYSXMLSTRINGS. On a different Db2 subsystem, High-speed Apply Engine requires this data to serialize your XML data correctly.

• If your input file contains XML column data, consider specifying a value of Yes for the LargeStatementSupport parameter to accommodate the larger amount of data.
• XML columns (and the XML table spaces that correspond to them) can be logged or not logged at the discretion of database administration personnel. If an XML column is not logged when the logical log input files are generated, High-speed Apply Engine inserts default values into that XML column in the target table.