If Connect CDC stops capturing changes, here is a checklist of things to do:
-
Check whether the change capture mechanism is still on. If not, it affects:
-
DB2 logging
-
Triggers
-
Check with the DBA and applications group to see if they have performed some maintenance on the table(s).
-
Was the table dropped? If so, the change capture mechanism was removed too. In such cases,
-
In Oracle, Sybase, Microsoft SQL Server triggers are dropped with the table.
-
In DB2/400, the “journal/jrnlrcv” information was lost.
-
In Microsoft SQL Server and Sybase, check whether the user triggers were updated. Connect CDC wraps user triggers and the Connect CDC portions could have been lost when the trigger was replaced.
-
Check whether you are using the replication user to make changes.
Changes made by the replication user are “ignored” by change capture triggers.
-
Are the table(s) removed from sending? Reselect tables for distribution in Connect CDC Director, validate and commit the model, initiate Model Update in Connect CDC MonCon.
-
Check whether the model was changed recently. If so, go to Connect CDC MonCon and do a Model Update.