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.
Add session-level reset for monitoring metrics in the MON_GET* table functions
There is no way to reset the metrics reported in the MON_GET* table functions. Please add functionality for resetting these at the session level, much like "RESET MONITOR" does for snapshot monitoring. Yes, there are a dozen ways to code this your...
Warning error code for Db2 tablespace architecture limit
If Db2 tablespace reaches architecture limit of 90%, then there should be a Warning Message write into db2diag.log, so that before it is reaching 100% of Db2 tablespace architecture limit, this can be fixed.
Now we are monitoring through a S...
implicit GRANT EXECUTE to SYSMON authority for all monitor routines(RIMS)
Customer has to grant the EXECUTE privilege on the monitoring functions to a user who already has the SYSMON authority. They would expect that a user of the SYSMON_GROUP holds this privilege implicitly. This looks like a restriction to the monitor...
MON_GET_CONNECTION is lacking CODEPAGE of connection
A 3rd party application connects to Db2 and we get SQL0302. The 3rd party vendor figures out, it is a double conversion to UTF-8One of the most valuable debugging informations was the codepage of the connection to the database, which is available ...
Application status change time is not available in any mon_get_* table functions
In snap admin views, users could see STATUS_CHANGE_TIME column for the application which was helpful in determining when exactly the application changed it status when investigating performance issues. This would help users to estimate or know how...
In the case of a hang, we only have the material for root-cause analysis if we were able to collect db2fodc information before the system became fully unusable. A small moving window of such information written out to disk on a regular basis would...
Index reorg information in a SNAP* view or a MON_GET* table function
Please make index reorganization progress (not table reorganization) accessible via a MON_GET* table function. Right now, it is only available via db2pd -d dbname -reorg -indexes and that is nearly impossible to parse via script.
An analog of LOG_HADR_WAIT_TIME monitor element is needed at the agent level
Sometimes it's very useful to understand HADR influence on the transaction performance. We do have a couple of related elements - LOG_WRITE_TIME and LOG_HADR_WAIT_TIME at the whole database level, but their values can't help us to understand, if H...
Expand db2pd -reorgs index to cover index rebuilds
Currently, there is no way to monitor index rebuild progress using db2pd. It will be useful for customers to be able to monitor index rebuild progress as they do for index reorgs (db2pd -reorgs index).
Do not place IBM confidential, company confidential, or personal information into any field.