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

Workspace Db2
Created by Guest
Created on Feb 22, 2022

Improve Standby Replay Performance

In our environment, the replay on the standy database is not able to keep up with the speed at which the PRIMARY is able to process data. Our replay gaps often exceed 100 GB, and this means that any failover would be delayed. We use HADR for high availability and we cannot tolerate a downtime of more than a few minutes. Our primary database can process at around 75-100 MB per second but the replay on the standby maxes out at around 40 MB per second. This means that on busy days, we quickly build a large replay gap on the standby, and if a disaster was to occur and we needed to failover, it would take too long and cause major outages. We need the replay speed to be faster.

We also use the reads on standby feature for certain reporting functions, but we cannot tolerate a time difference between the primary and the standby of more than 30 minutes. Unfortunately, because of the large replay gap, the time difference between the PRIMARY and the STANDBY will often exceed the 30 minute threshold, causing those jobs to fail.

Needed By Yesterday (Let's go already!)