IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

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:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Add a new idea Subscribe
Status Not under consideration
Workspace Replication: Q-Replication & Availability
Components Q Replication for Z
Created by Guest
Created on Sep 9, 2020

RELATED IDEAS

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.

Needed by Date Jan 1, 2021

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.