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 Future consideration
Created by Guest
Created on Feb 25, 2022

CDC for DB2 LUW - Refresh "RS" record is out of order - add DB2 Parameter CPU_PARALLELISM in CDC

When performing a Refresh to a DB2 LUW Target, then there is a record with Entry Type "RS" written to the target table, before the data records follow up with Entry Types "RR" only. The background of the first artificial "RS record" is to be able to distinguish between different Refreshes. Imagine you perform two refreshes directly after each other, there would be no criteria (in IBM CDC) to distinguish between them. IBM tried to solve that circumstance with the "RS record", however this record relies totally on the correct order to be written to the target, i.e. first RS record, then all RR records. Per default IBM uses export files and the DB2 Load Utility for the target refresh, but then the target database coordinates the load and can execute the load in parallel. In that case the RS record is somewhere in between the RR records and thereby out of order. The idea/solution: The Load Utility has a parameter CPU_PARALLELISM, which has to be set to 1 (no parallelism). Then the RS and RR records would be in the right order (we have tested it). So there should be added a new data store system parameter to configure that in the Management Console. Currently we use jdbc for refresh as workaround, which gives us the correct order, but which is much slower.
Needed By Month
  • Admin
    Apr 5, 2022

    Thank you for your help & support in raising this IDEA. We have reiewed this and agree this is a valid requirement. We will include it for consideration when we are developing the next iteration of our roadmap . At this point we do not have a commmitted date but will continue to monitor for additional customer demand.,