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 Future consideration
Workspace Db2
Created by Guest
Created on Dec 15, 2015


Currently BLU CDE tables only have the RECLAIM EXTENTS option of REORG enabled. This does not physically move rows and therefore REORG cannot reclaim extents unless 100% of the rows in an extent have been deleted (via deletes or BLU updates). Also, synopsis rows don't get removed unless every row in a range of 1024 rows have been deleted (or updated)

A manual work-around whereby "dummy updates" are performed on ranges of rows on the base table is possible, but is neither elegant or particularly efficient.

The preferred solution would be for REORG be extended to look for extents or TSN ranges that have a significant percent of deleted tuples. REORG should then move the remaining live rows to the end of the table, to allows those extents to be reclaimed and/or synopsis rows to be removed.

Note that Development (the DB2-CE CDE Storage team) have been involved in the PMR with comments in CRM / RCT.
  • Guest
    Mar 10, 2021

    My client uses ADMIN_MOVE_TABLE on column org tables as a workaround for Reorg - they would also be happy with a more extensive REORG functionality.

  • Guest
    Mar 8, 2021

    Dubai Islamic Bank using IIAS raised similar concerns and opened PMRs complaining inefficient reclaim process that is resulting in inorganic storage consumption.

  • Guest
    Mar 8, 2021

    Our client - Eurobank - is asking for this.
    Their daily ETL process deletes chunks of data from specific target tables, resulting in sparse tables that grow in size. We need a "table defragment functionality" within the db2 REORG.