IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
Clients:

  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity. http://ibm.biz/IBM-Data-and-AI-Portal-Register

Additional Information:

  • The shorter URL for this site is: https://ibm.biz/IBM-Data-and-AI-Ideas

  • To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Ignore log records for a dedicated subscription in IGNORETRANS

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:

  1. remove subscription from setup and restart Capture

  2. 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.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Sep 9 2020
  • Future consideration
Replication: Q-Replication & Availability / Q Replication for Z
Who would benefit from this IDEA? Replication admin, business user
How should it work?

The requested enhancement is to

  • enrich the IGNORETRANS option with a subscription name / sub_id to only skip log records for a dedicated sub

  • optionally enrich IGNORETRANS to specify how many log records to skip for the subscription

  • add some metadata to the Capture log (or to a "bad" file) to indicate which log record / which row was skipped if possible, to open up for options to bring back the data with alternative means

×

Attachments Open full size

Idea Priority High
Priority Justification see description
  • Attach files

Related ideas

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 "anonymous@euprivacy.out" 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