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 Oct 6, 2014

Perform rebuild of each index (for a table) in its own transaction

In the current design, all the index rebuilds for a table are performed within the same transaction (as the action that triggered them). If the transaction is interrupted (e.g. user interrupt or dropped session), then the entire transaction is rolled back; upon the next access, all the indexes have to be rebuilt again, even for indexes that were rebuilt previously. This can be a significant problem for large tables and/or tables with many indexes, for which the index rebuild transaction may take hours.
  • Guest
    Nov 9, 2019

    The major benefit of this would be to reduce active log space consumption. The impatient administrator that terminates index creation in the middle is not my concern. The other feature request is addressing this.

  • Guest
    Nov 8, 2019

    Would this feature still be required if index rebuilds were done asynchronously, such that an interrupted connection/session would not terminate the index rebuild process?
    (See RFEs DB24LUW-I-338 (index rebuild at first access) and DB24LUW-I-427 (index rebuild at restart)).