Skip to Main Content
IBM Data and AI Ideas Portal for Customers


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:

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

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

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


ADD A NEW IDEA

FILTER BY CATEGORY

Monitoring

Showing 62 of 12649

To monitor system resource usage at database level in a pureScale environment

All current monitoring facilities can not meet customer requirements to monitor overall system resource consumed for a specific database, in a database consolidation scenario of pureScale. PMR#: TS000078803
over 4 years ago in Db2 / Monitoring 0 Not under consideration

deadlock better diagnostic page dump in DIAGPATH

Ref TS000003442, PMR 68950,664,706Ref PMR 67845,664,706In case a deadlock occurs on MDC tables on BID index, diagnostic from Locking Event Monitor is not sufficient to understand deadlock. We need to understand data in conflict pages to check acce...
over 4 years ago in Db2 / Monitoring 0 Not under consideration

Add synopsis tables and Columnar Page Map usage to BLU explain plans.

Add synopsis tables and Columnar Page Map usage to BLU explain plans.
over 4 years ago in Db2 / Monitoring 0 Not under consideration

Enhance the db2pd flag -quiesceinfo

The following db2pd flag, -quiesceinfo, only applies to PureScale even though this is not clearly documented. We would like to see this available on all DB2 LUW installations.
over 4 years ago in Db2 / Monitoring 0 Not under consideration

Add a db2pd option to monitor rollbacks

Add the abiity to monitor rollbacks via db2pd
about 5 years ago in Db2 / Monitoring 1 Not under consideration

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...
about 5 years ago in Db2 / Monitoring 1 Not under consideration

Please add Firstlsn to the MON_GET_CONNECTION table function

The firstLSN is only available using db2pd. It is the ninth column reported from: db2pd -transactions It does not appear to be anywhere else. I would like to be able to query it using the MON_GET* table functions.
over 5 years ago in Db2 / Monitoring 0 Not under consideration

Lock event monitor does not log hex values of prepared statements

When using the lock event monitor to track prepared statements involved in lock timeouts/deadlocks, it was observed that parameter marker values for hex entries are not logged even though the option for history and values is enabled. This works fi...
almost 6 years ago in Db2 / Monitoring 0 Not under consideration

db will be blocked and hang after mon_heap is run out

agents will be blocked and will hang after mon_heap is run out when database turns on event monitor. Now it is works as design, yet customer hope we can change the design and decouple between event monitor and the agents executing some SQLs. So ag...
over 6 years ago in Db2 / Monitoring 0 Not under consideration

Invoke the DB2 call-out scripts (COS) for ALL First Occurrence Data Collection (FODC) events

Currently the DB2 call-out scripts (COS) will not be invoked for all ALL First Occurrence Data Collection (FODC) events. For instance the only time that FODC_AppErr% events will invoke the db2cos script is when the condition happens on a sub-agent...
almost 7 years ago in Db2 / Monitoring 0 Not under consideration