In very rare cases Db2 cannot provide log records for Q Capture, e.g. in case of a version mismatch, a compression dictionary error, etc. Removing the subscription and reloading the target is a practical approach. But in some situations (e.g., non condensed target table history, for example for regulatory use cases) reloading the target is the 2nd best option.
Today we have the following options:
remove subscription from setup and restart Capture
use IGNORETRANS to skip the transaction
With option 1 we lose a lot of changes for a table, as the subscription can only be brought back with a SIGNAL with a potentially big pause (depending on how long it takes to diagnose, remove the sub, restart Capture, add the SIGNAL).
With option 2 a lot of subscriptions can be effected, and it is really hard to diagnose which subscriptions (especially those without a problem) suffer from data loss due to the skipping of a complete transaction.
The requested enhancement is to enrich the IGNORETRANS option with a filter to be able to react specifically in case of a problem as described above.
|Who would benefit from this IDEA?||Replication admin, business user|
How should it work?
The requested enhancement is to
|Priority Justification||see description|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "firstname.lastname@example.org" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions