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,
Post an idea
Upvote ideas that matter most to you
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.
Improve the way HADR retrieve light scan on standby deals with failures such as DISK FULL
When DB2 HADR Standby is behind 2-3TB, it retrieves all files from archives to active log file system and makes the file system full. Standby replays one log file at a time and hence, retrieving thousands of files ahead slows down the replays, makes the active log file system full; Hence, light scan log retrieval will impove the HADR REPLAY on standby databases.
IBM case for reference: TS005525495
IBM development team agrees with our finding and proposed solution to provide an option like HADR_SPOOL_LIMIT for this issue; If an APAR can be included in DB2 12.x, it will not only help Department of Homeland Security / Custom and Border Protection but also to many other clients whose database is very large and very active.
From IBM HADR development team:
Our proposed solutions are:
Improve the way HADR standby receive logs so that it prioritizes more efficient method, such as retrieving directly from a shared archive, over others such as log shipping. This should allow HADR Standby to fully utilize the shared archive, until it catches up with primary.
Improve the way retrieve light scan on HADR standby deals with failures such as DISK FULL, so that HADR standby stick to log retrieving as much as possible, even if there are temporary errors.
Allow user to control the maximum disk space usage in active log path, including both active log files and retrieved log files in subdir of active log path. This prevents HADR standby from using up too many physical disk space when retrieving.
Do not place IBM confidential, company confidential, or personal information into any field.