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 Future consideration
Workspace Db2
Created by Guest
Created on Aug 29, 2023


Beginning Db2 v10.5, REORG RECLAIM EXTENTS on ITC tables also implicitly performs sparse extent consolidation before freeing empty extents (

However, the problem is that the "sparse extent consolidation" currently uses the same in-place reorg code and process, which does not have a lock timeout. During this phase, REORG RECLAIM EXTENTS on ITC can sit in lock-wait for several hours when there is a long running query holding an 'S' reorg lock on the pages being reorg'ed. As a result, the reorg can hold Db2 transaction logs for several hours, risking database transaction log full.

Instead of having REORG RECLAIM EXTENTS on ITC table to always perform the (in-place) "sparse extent consolidation" implicitly, we need more flexibility and want to see the "in-place" part being decoupled from REORG RECLAIM EXTENTS on ITC tables. The following features are suggested to be added and to allow these options in an auto-reorg policy:


1) Allow REORG INPLACE command on ITC table, and have REORG RECLAIM EXTENTS to do only free extent reclaim, or

2) Add a new option to REORG RECLAIM EXTENTS command to only perform extent reclaim with no "sparse extent consolidation",

3) or both 1) and 2)

Needed By Quarter