Skip to Main Content
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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Future consideration
Created by Guest
Created on Sep 26, 2019

CDC for DB2LUW shall leverage HADR/pureScale features like WLB, ACR

From some of the recent experiences, it occurred to me that for CDC for DB2 LUW there could be better ways of handling HADR node/pureScale member failover. As we rely on CLI (native calls) to read source logs, the connection api (SQLConnect) does not consider driver cfg file (db2dsdriver.cfg) that contains information about failover and alternate servers. The connection api we should be using is SQLDriverConnect() which then reads from db2dsdriver.cfg to set all the connection options.

I think it's worth spending some effort in assessing this change. Currently there are CDC specific settings to account for failover that are not acceptable in some cases (like manual inventions). I don't know how QRep has this implemented, but we can give a try.

Note: This should be only source side change. For target when we change to Type 4 all the failover properties can be specified from CDC cfg tool.