Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

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

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.

Additional Information

To view our roadmaps:

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

IBM Employees:

The correct URL for entering your ideas is:

Status Planned for future release
Components Q Replication for Z
Created by Guest
Created on May 3, 2017

ALTER table DATA CAPTURE NONE not detected by IIDR QREP or CDC

If 'ALTER table DATA CAPTURE NONE' is executed against a table that is actively replicating, any changes made to the source data will not be captured or replicated until ‘ALTER table DATA CAPTURE CHANGES' is executed. This would cause the target table to be out of sync with the source table. There are no messages or indications by Capture for when the DATA CAPTURE NONE is in effect for an actively replicating table.

IIDR QREP and CDC should be able to detect when a replicating table changes to DATA CAPTURE NONE. There should be some message or warning to indicate this. Since Insert/Update/Delete activity would not be captured at that point, it has the potential to cause data out-of-sync conditions. Recovery could be difficult especially for bi-directional replication.