Suggest an Idea

[Wim]

Some tables that are heavily updated on the source during a full reload of that table on the target, generate duplicate insert errors.

This is a known issue described in much detail in the QLIK KB here. 

However, since version 6.6 the workaround described in that article no longer works, and produces an error. The syntax of the string that needs to be put in the table settings has changed.

I open this request to have this formally implemented as a feature/option that should be enabled by default for DB2 z/OS or DB2 AS/400 databases. Currently it is a "hidden" internal feature to workaround this issue, and thus not supported and not stable.

It is crucial for our business that this gets implemented.

Related case: 02138955 - INITIAL LOAD FAILS WITH DUPLICATE INSERT ERRORS WHILE APPLYING CACHED EVENTS.

[Shelley_Brennan]

Thank you for the suggestion.  We will continue to collect feedback from others as well.

[Shelley_Brennan]

Improvements here are under development.  Thank you!

[Wim]

Hello, do you have an idea what release this will be available in?

We are planning a product upgrade and consider waiting for this if it's not too far away. Thanks.

[Shelley_Brennan]

It is a candidate for the Nov 2021 release.  I don't think it will be available sooner than this.  Thanks!

[Shelley_Brennan]

This request has been implemented for DB2 z/OS sources in our upcoming November release.  Technical Preview for this release should be out later this week.  Please take a look and provide any early feedback.  Thank you!

[Shelley_Brennan]

This has been addressed for DB2 z/OS sources in the Nov 2021 release of Qlik Replicate.