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:

Created by Guest
Created on Jun 22, 2021

Avoid lock table on full refresh process

We have been contracting the IIDR for z/OS a long time but just Q Replication was used until 2 months ago, so when we started to use the CDC for DB2 with target CDC Kafka in development environment we see that a lock table in source table is done when refresh command is executed on subscription. This is an important issue that can cause a big problem on production environment due to possibility of happen a lot of timeouts and unavailable resources. We know that Q Replication has the similar process to execute refresh but this kind of lock is not done diminishing the risk of outages on source environment. Another issue that we know that CDC for IDAA had the same issues on V3/V4 that was solved by IBM, why had CDC DB2 "pure" not this enhancements applied ?

Needed by Date Jul 15, 2021
  • Admin
    Aug 26, 2021

    Thanks for raising this IDEA. We have reviewed the suggestion and agree this is a valid requirement . It is currently in development - we will notify you when it is available.