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

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 (

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 updates on 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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

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