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 Employees should enter Ideas at

Status Not under consideration
Workspace Db2
Created by Guest
Created on Sep 16, 2015

Asynchronous index rebuild on first access

Pain point: Index rebuild stops if user terminates the connection accessing the table with an index that is marked inconsistent and it starts over from the beginning again on next table access by another user.

An index object is marked invalid and needs to be rebuilt. In our case, an offline table reorg was canceled while in the offline index rebuild phase. The next access to the table will drive index recreate. If the next access is made by a user application, it is possible that this application might time out. The result is that the work performed by the index rebuild is lost and we need to start from the beginning on next access. If the subsequent accesses to the table are made by user applications, then we might never complete the index build until the database administrator steps in to correct the problem.

Ideally DB2 should rebuild the index object asynchronously and have the agent that first accessed the table wait behind that rebuild. This way if a time out is hit by the user application, the index rebuild can continue uninterrupted. Subsequent access to the table will then wait behind the index rebuild and they are free to time out as well. The index rebuild can complete in the smallest amount of time possible without the intervention of the database administrator.

Please update us on the progress of this request.

Thank You.