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
Enhance Db2 WLM to enable it to prioritize access to physical I/O
We have a Db2 AESE 11.1 fp4a mixed use (but no column tables) data warehouse on an AIX 7.2 LPAR that is limited to 75K IOPS by NetApp. When the threshold is met, high priority OLTP queries submitted by our 1000 retail store POS systems can hang indefinitely. These are normally sub second queries, but can take 30 min or more to complete during periods of IO throttling. The front-end application will time out before then, but not without negatively impacting our store operations and customer experience.
Db2 WLM is used to prioritize our workloads, but that primarily controls access to CPU and prefetch priority, and is not effective in this situation. We'd like the ability to prioritize access to physical I/O for high priority queries, especially during times that IOPS is limited by a NetApp threshold.
Failing that, it would help us if db2 provided a way to identify which queries are contributing the most to the high IOPS that NetApp sees, so we could consider selectively terminating those queries.
Do not place IBM confidential, company confidential, or personal information into any field.