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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


179 VOTE
Status Future consideration
Workspace Db2
Created by Guest
Created on Oct 11, 2019

Reduce Time Required for Online(Inplace) Reorg for huge tables

1) Inplace reorg will take time more for the tables with huge data say for example 1 TB

2) To Reduce the time for this we want to avoid full table scan hence we need to look in portions of the data in a table where it is getting fragmented

3) Hence for this if we have special pages on a disk which stores this data that are fragmented on a table where huge transactions are on

4) These special pages should be as part of the table or index object

5) Reorgchk command should be inherent with the capability of displaying the tables that needs Reorg and also portions of it where it has got fragmented

6) If this feature is enabled we can overcome the disadvantage of the extra space needed by the admin_move_table which uses the concept of Load from cursor inside it


Needed by Date Oct 14, 2020
  • Guest
    Jun 6, 2021

    Very much needed feature. I can relate it to an issue we have at present where we are not getting downtime from customer as the table is huge and is pending for very long time resulting in performance issues. It wil be very beneficial for both, us and the customer.

  • Guest
    Jun 4, 2021

    Good idea

  • Guest
    Jun 2, 2021

    There are customer who does not use online reorg because it takes a long time for huge table, reducing time will help them to save down time for offline reorg. Good idea!

  • Guest
    Jun 2, 2021

    Good idea!! The customer will save lot of down time for the Offline Reorg , if this idea gets implemented in Inplace Reorg and also the execution time improves. It will say save lot of time and cost for the customers!

  • Guest
    May 30, 2021

    To me this seems a key improvement feature for DB2 which makes the DB2 experience for our clients more valuable.

  • Guest
    May 28, 2021

    Let me add, this idea would be very beneficial to many customers. TIme and resource saving are critical and this feature would appeal to many customers.


  • Guest
    May 28, 2021

    I like this idea

  • Guest
    May 25, 2021

    It a good alternative to minimaze downtime for customers in a days downtime is becoming more and more unacceptable and high availability is crucial for clients

  • Guest
    May 25, 2021

    As this procedure is critical to keep the database performance and healthy , reduce this time will help customers to not have a huge maintenance window to execute the procedure and keep the environment up and running in its best way.

  • Guest
    May 25, 2021

    I like the idea , I remember when I was working with Commerce on Cloud, we used a tool called db2collect. Have you heard? So through db2 collect I understood what tables should run reorg. The procedure was very critical, imagine a Transactional table for an e-commerce site. The maintenance window was not large. So this idea matches a lot the requirements related to an e-commerce workload.

  • Guest
    May 24, 2021

    This feature could be beneficial, especially if you can reorg within a data partition

  • Guest
    May 20, 2021

    It will a good feature to add.

  • Guest
    May 20, 2021

    Good Idea it's really useful.

  • Guest
    May 20, 2021

    It is a great idea!

  • Guest
    May 19, 2021

    It is a great idea, we have faced a lot of times with the extra fs problem from OS point of view, it is required an extra prepare task for example requests of extra disks for the LUN if there is no free capacity in the vg, another benefit, if we are in the special case and we have to perform online reorg during daytime, this solution help to us to reduce the time of the performance related problems during the reorg is running when the customer is using the database.

  • Guest
    May 18, 2021

    The idea of only doing a reorg of "sparse" pages or pages with a large % of overflow records as an added option to inplace reorg seems like a good idea and could potentially reap a large time savings compared to a full scan reorg while still providing needed I/O efficiency to SQLs that scan large numbers of pages.

  • Guest
    May 18, 2021

    Its a Nice idea.

  • Guest
    May 17, 2021

    Awesome Idea.


  • Guest
    May 17, 2021

    It is really a Great Idea, many customers, like SCOR, has rised their interest in a such feature.

  • Guest
    May 14, 2021

    This is a great idea, a full table scan considerably, it is still one of the most expensive operations. It can consume a considerable amount of CPU time.The inplace reorg will avoid the performance issue on the server.