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
In a HADR configuration typically customers use db2pd -hadr on the standby to monitor the state. On the standby if there is a problem with one of the tablespaces it'll be marked invalid and future log records against the tablespace will be skipped. If one continues to monitor the state of HADR via db2pd -hadr the peer state will remain potentially missing the tablespace issue.
Update the db2pd -hadr command hinting to the potential problem.
The requirement is also described at https://db2wiki.torolab.ibm.com/index.php/HADR_performance_monitoring#Alert_user_about_abnormal_tablespaces_on_standby
Alert user about abnormal tablespaces on standby
Tablespaces can be in abnormal state on standby. Common causes are replay error on the tablespace and media error. Standby will skip log records associated to abnormal tablespaces. At database level, the db will appear normal. This can be misleading to users.
At takeover time, we do loop through all tablespaces and print warning on abnormal ones into db2diag.log. But that message can be easily missed by DBA and may be too late.
The proposal here is to add a warning flag to the usual HADR monitoring fields indicating some tablespaces are in abnormal state. For consistency, this field should be applicable on both P and S. The flag should be updated whenever tablespace state changes.
Do not place IBM confidential, company confidential, or personal information into any field.