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 Oct 17, 2018

Online Reorg takes 10 times the size of the table in logs to complete

Note - case id TS000861837 (it won't let me inter this in the pmr)
See example provided in pmr.
Some table take more than 10 times the size of the table in logs to complete.
There seems to be very little in the way of documentation that I or the pmr analyst could find supporting the extent of this behavior (at least there needs to be a big warning imo).
From the pmr I am told that this is working as designed as far as IBM are concerned which I find difficult to fathom.
A similar reorg in Z/OS uses minimal logs as it builds a second copy and then flips the two copies - just like db2 luw index reorg.

Either the current online reorg should be changed to reduce the log usage or the same method that is used for indexes (and db2 z/os uses for tablespaces) should be available as an option for table reorgs.