Limitations and considerations

You should be aware of the following limitations and considerations when using an IBM DB2 for iSeries source.

• Multi-member (Partitioned) tables are not supported

• Field level encryption is not supported

• Journal receivers must be System Managed rather than User Managed.

• Journals containing minimized data are not supported.

  The MINENTDTA parameter should be set to: MINENTDTA(*NONE)

• All tables must be in the same journal
• The XML data type is not supported
• The DBCLOB data type is not supported
• Row size cannot exceed 32740 bytes

• Usually, Replicate only applies source database changes to the target if the transactions with the changes were committed before the Full Load started. However, records that were deleted from the source as part of an uncommitted transaction will not be replicated to the target during Full Load.

• DELETE operations in auto-commit mode will be ignored for tables journaled with *AFTER images. In such cases, DELETE operations will only be captured if one of the Add RRN column options is enabled and is set as the only Primary Key.
• When auto-commit=ON, the timestamp of the last committed transactions will be displayed as "01-01-1970 00:00" in the SOURCE_CURRENT_TIMESTAMP column of the attrep_status Control Control table.
• Replicating columns, tables, and libraries with special characters in their name is not supported.
• Tables created by DDS: If you need to replicate tables created by DDS, please seek guidance from Qlik Support or your Qlik Customer Success Manager.

• Replicating data with 4-byte emoji characters is not supported.

• When the Use table and schema system names option is enabled (in the endpoint's Advanced tab), only table/schema names that contain uppercase letters, digits, and underscores (_) are supported.

  For more information on this option, see Replicating System Names.

• Remote journals are not supported.

• The DROP TABLE DDL is not supported
• The RENAME TABLE DDL is not supported