Limitations and considerations

When using IBM DB2 for LUW as a data source, the following limitations currently apply.

• Clustered database is not supported

  Information note

  Users can define a separate IBM DB2 for LUW database for each of the endpoints in the cluster.

• Changes to DECFLOAT columns will be ignored during CDC.
• The RENAME COLUMN statement is not supported.
• When performing updates on MDC (Multi-Dimensional Clustering) tables, each update is shown in the task monitor as INSERT + DELETE.
• Variable-length string columns with data that is stored out-of-row will be ignored. Note that this limitation is only applicable to tables created with extended row size.

• The Purescale environment is supported using the Start processing changes from source change position Run option only.

• If you need to replicate 4-byte emoji characters, use a transformation to convert the data type from STRING(n ) to WSTRING ( n*2 ).

• When truncating a table with multiple partitions, the number of DDL events displayed in the Replicate console will be equal to the number of partitions. This is because IBM DB2 for LUW records a separate DDL for each partition.

• The following DDLs on partitioned tables are not supported:

  • ALTER TABLE ADD PARTITION
  • ALTER TABLE DETACH PARTITION
  • ALTER TABLE ATTACH PARTITION
• When the Replicate LOB columns task setting is disabled, any table that has LOB columns will be suspended during change processing.
• When the Audit table option is enabled in the Store Changes Settings tab, the first timestamp record in the audit table will be NULL.
• When the Change table option is enabled in the Store Changes Settings tab, the first timestamp record in the table may be Zero in some cases (i.e. 1970-01-01 00:00:00.000000).

• When capturing changes to source tables, a RENAME TABLE operation will be captured only if it is preceded by a DML operation.