Data Replication does not replicate DDL changes to Apache Kafka targets.

Data Replication does not replicate DDL changes for bidirectional replication. For each of the two one-way configurations that you use for a bidirectional replication, Data Replication does not support unidirectional replication of DDL changes.

If you try to edit a replication configuration for which DDL capture is enabled while a running replication task is processing a DDL change, the Data Replication Console displays a message that asks whether to stop the running replication tasks. If you edit the configuration while the tasks are processing a DDL change, you will not be able to save your configuration changes.

Data Replication does not support replication of FOREIGN KEY and CHECK constraints.

Data Replication does not support replication of RENAME TABLE operations.

Data Replication does not support replication of the DEFAULT clause. When replicating a source DDL statement that uses the DEFAULT clause, the Applier executes the equivalent statement on the target without the DEFAULT clause.

For MySQL sources, Data Replication does not support DDL replication for tables that have columns with the JSON datatype or with spatial datatypes such as GEOMETRY.

For Oracle 12

c

sources, Data Replication does not support replication of the IDENTITY clause in source DDL. When a source DDL statement contains the IDENTITY clause, the Applier executes the equivalent DDL statement on the target but without the IDENTITY clause.

Data Replication does not support the replication of ALTER TABLE partition operations such as ADD PARTITION, SPLIT PARTITION, and DROP PARTITION.

Data Replication does not replicate DROP COLUMN operations for the following types of columns that are involved in conflict resolution:

Columns for which source and target values are compared to detect Update conflicts
Columns that you use as resolution columns for the Maximum and Minimum resolution strategies
Columns for which you use before and after images as custom procedure parameters

Data Replication does not replicate DDL operations that drop the last mapped table or column.

To replicate DDL operations that change indexes or primary key constraints on the source to existing indexes and constraints on the target, ensure that the names of the target indexes and constraints match the names of the corresponding source indexes and constraints.

When the Applier runs in continuous mode and a DDL change occurs on a DB2 source, the Applier applies the DDL change only after the Extractor processes the subsequent DML change record for any mapped source table.