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 Delivered
Workspace Db2
Created by Guest
Created on Jan 25, 2018

New DB2 for LUW Automated Failover Option

DB2 HADR - TSAMP integration. Treat a set of databases on a server, even across DB2 instances, as a unit. If one database has a failure and has to failover then we want all the databases in that unit to failover. And just as important, we want to use one virtual ip for this unit.
  • Guest
    Oct 21, 2019

    I understand this problem, I've had it myself with 6 databases of IBM BPM. But on one day, the cluster wanted to fail over and had an issue on the other side. So a few databases managed to stay there and the rest failed back.

    the customer mainly stayed online, although this is not licensed as active-passive cluster anymore.

    What shall happen, in the perspective of this idea, if such a situation happens again? Failing completly? Failing back and forth until an admin is stopping this? Leaving the cluster in a stable but distributed configuration?

    i voted for your idea, but I'm looking forward what IBM comes up as a solution. Maybe I can implement then this at my customer.