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: 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

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Created by Guest
Created on Nov 30, 2021

Support for key updates for Fast apply method ParallelizeSingleTableByHash

We are using ParallelizeSingleTableByHash for oracle target. This has resulted in extremely fast processing by the apply. However for certain tables when they have key updates, the delete and insert can result in different hash key and hence they are handed off to different agents and depending on conditions the insert may happen before the delete resulting in unique violations. when this happens, apply will try to serialize the transactions and hence cause a spike in latency for close to 15-20s.

Due to this we need to move such key update tables into a separate subscription which doesnt have fast apply by hash. this is operational not good to move the subs and also other fast apply does not provide such low latency as hash method.


Apologize to draw comparisions but QREP for oracle target handles such key updates seamlessly. so CDC should be able to do this.

IBM has acknowledged that this is a bug in fast apply and i am now requesting this RFE t fix this issue permanently.

Needed By Yesterday (Let's go already!)