We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
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:
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.
Do not place IBM confidential, company confidential, or personal information into any field.