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 May 30, 2019

Avoid the database, configured in HADR, on primary side experience an outage when the database on the standby side experience any problem.

We use Db2 pureScale in many environments using POWER System. For our disaster recovery strategy we use HADR for each database between sites. In a specific situation of when some standbys databases experienced HADR_FLAGS = STANDBY_RECV_BLOCKED, registered on Case TS002294790, we got an outage of the application because this issue on the Standby let the databases on the Primary side to stay unavailable (deactivated the database).

Needed by Date Dec 31, 2019
  • Guest
    Jun 28, 2019

    I am rejecting this request. I reviewed case TS002294790. The so-called primary "outage" when standby in STANDBY_RECV_BLOCKED condition is just the implication of congestion (meaning primary can no longer send logs to standby, ie. the tcp/ip send() call is not going through. Such can be caused either by slow network, or slow log replay on the standby. In TS002294790 it was slow replay (because STANDBY_RECV_BUF_PERCENT and STANDBY_SPOOL_PERCENT are at 100%). When in congested state, the impact on primary is that no more log records can be produced so will stop all transactions (that need to write log records). This has been the behaviour of HADR since the feature was first introduced.

    If user does not want the primary to be impacted by congestion, the recommendation is to configure HADR_SYNCMODE to SUPERASYNC.

    If there is anything to improve, it would be on the standby log replay performance. If customer is still affected by this problem, I suggest we reopen TS002294790 or open a new one, to see if there is tuning or other tactical solution can help. Otherwise, we can open new RFE (or change this one) to improve standby log replay performance.