Limitations and considerations

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

Limitations and considerations for all data tasks

• 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, excluding LOBs, cannot exceed 32740 bytes

• Usually, Data Movement gateway 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 moved 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 table.
• Landing 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.

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

• Table and columns names that include non-Latin characters (NLS) are not supported.

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

• Remote journals are not supported.

• Table or columns names that include NLS (non-Latin) characters are not supported.

Limitations and considerations for replication tasks only

• The DROP TABLE DDL is not supported
• The RENAME TABLE DDL is not supported
• In Batch Optimized Apply mode, when a table that matches the task's table capture pattern is created in the source database (CREATE TABLE), the table will not be created in the target database until a transaction occurs in any of the captured tables.