You can register only tables that are associated with physical files for change data capture.

The maximum length of a DB2 row or column for which PowerExchange can capture changes is 128,000 bytes.

PowerExchange cannot process journals for registered tables that include minimized journal entries. Verify that you do not use minimized journal entries. Use the CRTJRN or CHGJRN command on the source i5/OS system to set MINENTDTA to *NONE.

PowerExchange cannot capture changes that result from a Clear Physical File Member (CLRPFM) command or SQL TRUNCATE operation on DB2 for i5/OS tables that are registered for change data capture. PowerExchange CDC processing treats a CLRPFM command and TRUNCATE operation in the same way. i5/OS records only a single journal entry for all delete operations that result from a CLRPFM command or TRUNCATE operation. However, a single journal entry is not sufficient for PowerExchange to properly replicate CLRPFM or TRUNCATE deletions to CDC targets. By default, when PowerExchange encounters a journal entry for a CLRPFM command or TRUNCATE operation, CDC processing stops.

If you use SQL fast delete processing, SQL DELETE operations are not written to the DB2 journals. To use DB2 for i5/OS CDC, you must prevent SQL fast delete processing by setting a query option in the QAQQINI file. By default, the SQL_FAST_DELETE_ROW_COUNT query option specifies *DEFAULT. You must change this default by setting the SQL_FAST_DELETE_ROW_COUNT parameter to *NONE. For more information about this parameter and the query option file, see the IBM DB2 for i5/OS documentation.

For IBM i5/OS servers with a QPWDLVL password level setting of 3, PowerExchange supports mixed-case passwords and long passwords of up to 30 characters.

PowerExchange CDC does not honor Row and Column Access Control (RCAC) rules because of a DB2 limitation. When PowerExchange tries to process journal entries for tables that have RCAC rules applied, the columns or rows are not masked or filtered based on the rules. DB2 for i5/OS 7.2 introduced RCAC rules to help database administrators control the visibility of sensitive DB2 data.