replication tool should be able to track the changes happening on the source during the refresh period and then replicate them on to target accurately or handle the conflicts gracefully rather than terminating the whole replication process.

At Goldman, Infosphere CDC is setup in such a way that it starts every day at 2:30 pm ET, refreshes the target table(s)and keeps them in sync from that point. We started seeing issues recently where Infosphere terminates completely saying that there are duplicates on the target table though Infosphere is the only process that is updating the target. When we raised this query we were told that we have to either block any updates on source during the refresh or remove the primary key constraints on target table. Either of these options are not workable for Goldman as we keep getting trades through out the trade and we can’t block the source table from having any writes and we can’t remove the keys on the target table as it’s a vendor application that have limited access to. We believe, a replication tool should be able to track the changes happening on the source during the refresh period and then replicate them on to target accurately or handle the conflicts gracefully rather than terminating the whole replication process.

Needed By

Yesterday (Let's go already!)

Post comment

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Please enter your email address

RELATED IDEAS

replication tool should be able to track the changes happening on the source during the refresh period and then replicate them on to target accurately or handle the conflicts gracefully rather than terminating the whole replication process.