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.
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.