Oracle CDC by Attunity (SQL 2012) does not handle updated primary keys correctly - by stefang_1234

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 774367 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 12/14/2012 8:00:32 AM
Access Restriction Public


When a table has CDC enabled and the primary key is updated this should be treated as a delete followed by an insert. This is the behavior you get with SQL Server CDC, but Oracle CDC registers this as a normal update.

This problem makes it impossible to use cdc.fn_cdc_get_net_changes_<capture_instance> and MERGE to implement a simple replication.
Sign in to post a comment.
Posted by Microsoft on 8/30/2016 at 12:34 AM
Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SSIS. The reasons for closing these bugs are following:
1.     The fix is risky to implement in the current version of the product
2.     Scenarios reported in the bug are not common enough
3.     A viable workaround is available.

If the issue is a critical business interruption, please call CSS (Customer Support Services).

Thanks again for reporting the product issue and continued support in improving our product.
Posted by TRyanSkinner on 7/18/2013 at 12:32 PM
Ping? It's been 6 months since the last comment. Any word on this?
Posted by Faiz VP on 1/21/2013 at 2:36 AM
I haven't started implementing it yet but can anyone else verify that this bug exists?