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 Not under consideration
Workspace Db2
Created by Guest
Created on Mar 14, 2019

Db2 HADR PEER status enhancement

We would like IBM to look into adding an additional HADR state once the database comes into PEER.  In Db2 10.5, there is an additional parameter, STANDBY_RECV_REPLAY_GAP that can hold large amounts of transactions that need to be replayed due to the volume of the given database.  Due to maintenance or any other user initiated failover, HADR must wait for all of this to be replayed before completing the failover.  When you think about it then, PEER does not actually mean PEER anymore.  A 20 minute failover is not acceptable for a given database when using NEARSYNC because the volume and load is high.  HADR should show a status of PEER, STANDBY_REPLAY at the very least, and not allow a failover until this is completed.  It is not truly peer until this is done, and the standby is not ready to become primary until this is done, which defeats the meaning of PEER at this point. Similar to when the db is in remote catchup pending, when the logs between the primary and standby are at an acceptable level to be considered connected, so to should the STANDBY_RECEIVE_REPLAY_LOG_GAP be at an acceptable level to allow a fast failover (under 5 min, etc)

PMR ID: TS001986999

Customer ID: 3015177

  • Guest
    Jul 15, 2019

    No response, rejecting this RFE. Anyone still interested can reopen, with feedback on how you want the product to react, ie. 1) or 2) mentioned in the first comment.

  • Guest
    Jul 2, 2019

    Did not receive any feedback for my question above. If there is still no feedback for 2 weeks, I will reject this RFE.

  • Guest
    May 29, 2019

    Looking for feedback.  Say we let user specify a threshold for replay gap.  When it is reached, what do you prefer: 1) Db2 automatically drops from PEER state to RCU state; or 2) standby would delay sending ACK to primary until replay moves up ?  1) means no impact to primary but possible data lost on outage.  2) means no data lost but transactions on primary are held up.