For DB2 for z/OS source tables, PowerExchange can process change data from BLOB, CLOB, and DBCLOB columns, provided that the row size does not exceed 8 MB. PowerExchange reads the LOB data from the PowerExchange Logger log files instead of directly from the DB2 transaction logs.
PowerExchange CDC processing of LOB data depends on whether the data is stored fully inline in the base table space, as follows:
When BLOB, CLOB, or DBCLOB data is stored fully inline, the row size in the base table space is limited by the maximum DB2 page size of 32 KB. The DB2 ECCR can capture LOB data up to the inline length, provided that this length does not exceed the 32-KB page size limit minus the size of the DB2 control fields and the size of the columns. PowerExchange delivers the inline LOB data to PowerCenter workflows that use a DB2zOS CDC application connection.
When CLOB (including DBCLOB) data is stored fully or partially in an auxiliary table space, you can use the new generated DTL__ST column in the extraction map to determine if the CLOB data in the PowerExchange Logger log files is complete or incomplete. If the CLOB data is incomplete, you can use an Expression transformation and unconnected Lookup transformation in the PowerCenter workflow to retrieve all of the current CLOB data from the DB2 source table so that all of this data can be delivered to the target. Informatica recommends that you use a single target because the use of multiple targets can cause updates to be applied in the wrong sequence.
When a Lookup transformation is used to retrieve CLOB data, the before images of rows that contain the CLOB data are not available for an UPDATE or DELETE operation. However, the after images of rows that contain the CLOB data are available for an UPDATE or INSERT operation.
When BLOB data is stored fully or partially in an auxiliary table space, PowerCenter cannot retrieve all of the BLOB data because of limitations related to using binary ports in Lookup transformations. In this case, contact Global Customer Support to determine if a custom solution is available.
For more information, see the "DB2 for z/OS Change Data Capture" chapter in the