Hi Anton,
IBM Data Replication's CDC handles DDL in different ways for different source databases. It shouldn't be necessary to recreate subscriptions when there is a DDL change, but it may be necessary to remap tables and issue a refresh. Usually if replication ends because a DDL change was detected, the Event Log will contain a high-level description of how to recover.
If your source is Db2, then the
steps for planned DDL changes (without refreshing tables) are listed in Knowledge Center, and there are options for using either the Management Console UI or using commands. To find the steps for the various source database types, you can use
this search.
For Oracle sources, some DDL changes like adding table partitions are handled automatically (and changes to the newly added partition will replicate) without replication stopping.
If the DDL change is unplanned and the subscriptions didn't replicate to head of log, then you can use the steps for planned DDL changes but you will likely need to refresh the tables. You may want to look at using CHCCLP scripting to automate the process.
If you have any trouble, please reach out to our IBM Data Replication support team by logging a ticket at
http://ibm.biz/idrsupport.
Hope that helps,
Sarah
IBM Data Replication
------------------------------
SARAH ORVIS
------------------------------
Original Message:
Sent: Thu May 14, 2020 07:36 AM
From: Anton Kondratiev
Subject: DDL applied to source tables leads to subscription halt
We have a problem with sources which can modify structure of source tables - after modification appropriate subscriptions are stopping, we have to recreate them and the most annoying thing is that we have to reload all data. We have version 11.4. Is there any workaround for this problem?
------------------------------
Anton Kondratiev
------------------------------
#DataIntegration
#DataReplication