This portal is to open public enhancement requests against products and services offered by the IBM Data Platform 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 updates on 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
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Employees should enter Ideas at https://ideas.ibm.com
Our assessment of this request is that the current pain-point is due to network difficulties for the workload. Our suggestion is to improve network bandwidth or use SUPERASYNC.
If network is adequate, only experiencing congestion occasionally, then we suggest setting DB2_HADR_PEER_WAIT_LIMIT. Yes, the workload is still impacted for a period of time specified by the value of DB2_HADR_PEER_WAIT_LIMIT and the smallest value we support today is 1 second. If a smaller value for DB2_HADR_PEER_WAIT_LIMIT is needed, we can consider allowing syntax to specify value in ms.
May be we can few more factors like
network congestion for longer than x seconds
Or standby delays tolerated up to 2ms
Additionally, we can consider enabling the feature to revert the synchronization mode back to its original SYNC mode once certain criteria are met.
This would ensure that, after the temporary shift to ASYNC or SUPERASYNC, the system automatically restores full data protection when conditions stabilize.
By doing so, we can assure customers of both downtime resilience and performance maintainability, without manual intervention.