IncludeLOB

For Db2, the IncludeLOB parameter specifies whether the High-speed Apply Engine processes or ignores records in the logical log that apply to large object (LOB) columns. If you need to update LOB columns in the target tables, set this parameter to Yes.

Attributes

This parameter has the following attributes:

Attribute

Value

Section

[LogicalLog]

Abbreviation

None

DBMS

Db2

Required?

No

Valid values

Yes, No, Inline

Default value

Yes

Usage

Specify Yes to include LOB column data in the changes to target tables. Specify No when the source tables do not contain LOB columns or when they contain LOB columns, but you do not want to attempt to update the LOB columns in the target tables. Specify Inline to include only inline LOB data in the changes to target tables, ignoring the auxiliary LOB tables. The default value of this parameter is Yes.

Be aware of the following points regarding High-speed Apply Engine and LOB processing:

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

  • If your input file contains LOB column data, consider specifying a value of Yes for the LargeStatementSupport parameter to accommodate the larger amount of data.

  • A LOB table space that corresponds to a LOB column (or a partition of a LOB column) can be logged or not logged at the discretion of database administration personnel. If a LOB table space is not logged when the logical log input files are generated, High-speed Apply Engine inserts default values into the LOB column (or the partition of the LOB column) of the target tables.

  • When the value of the SQLType parameter is Undo, High-speed Apply Engine cannot apply changes to undo the effect of a delete action on a row that contains a LOB column. The logical log records that exist for a delete action on a LOB table space associated with a LOB column do not contain LOB column data. Consequently, High-speed Apply Engine cannot insert the data into the LOB column to undo the delete action. In this situation High-speed Apply Engine issues a warning message and either inserts default values for the LOB column or skips the LOB column and allows Db2 to insert default values.

  • When the value of the SQLType parameter is Undo, High-speed Apply Engine might not be able to apply changes to undo the effect of an update action on a row that contains a LOB column. The logical log records that exist for an update to a LOB table space associated with a LOB column might not contain the 'before image' of the LOB column data. If it cannot undo the effects of an update action, High-speed Apply Engine issues a warning message and either includes default values in the LOB column or skips the LOB column and allows Db2 to insert default values.

Related topic


Was this page helpful? Yes No Submitting... Thank you

Comments