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 (https://ideas.ibm.com).
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 updateson 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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
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)
Do not place IBM confidential, company confidential, or personal information into any field.