Skip to Main Content
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 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.