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:

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:

Status Not under consideration
Workspace Db2
Created by Guest
Created on Jul 20, 2017

DBA needs control over Jobs from Automatic Maintenance

We recently had an outage due to automatic maintenance - reorg on a table to reclaim extents.
Application A (db2hmon) was running a reorg reclaim on a table and Application B which was already connected to the database and was running a job, as a part of the job it was running a query on Admin_tab_info for querying the table storage properties. Application B was put on Latch wait, which Application A was holding. We tried increasing the secondary logs and then changed to -1 as well, however the reorg was running for over 14 hours and Application B was holding the first active log which eventually increased the log utilization in the database. Opened a PMR in meantime with IBM as well.
For over 16 hours of waiting, we were forced to take a downtime and restart the database in middle of the day which iss unexpected. Where the crash recovery took around 76 mins and later the database was up.
So we need a utility or an enhancement to control the jobs which are triggered by Automatic Maintenance