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 Delivered
Workspace Db2
Created by Guest
Created on Nov 12, 2014

Reorg pending after three ALTER TABLE statements is not useful in 24x7 environment

After three ALTER TABLE statements (depending on the clause, but an error can be forced by changing type from VARCHAR to CHAR ) table switches into reorg pending state. This state can only be resolved by an offline reorg.
Additional problem is that after a first strong ALTER TABLE (like changing VARCHAR to CHAR) no write operations are allowed.
In a 24x7 environment this is not feasible, DB2 is not online available for agile and rapid developed applications where schema changes are deployed regularly.
Add a new setting (db2 registry) to avoid
- unsupported write operations (UID) with error SQL0668N
- reorg pending state of a table with error SQL20054N
Write operations must be supported after ALTER TABLE statements and no reorg pending state must be reached.
  • Guest
    Jan 18, 2021


    You are not missing anything. The registry variable to block ALTER TABLE operations that would put the table into "reorg pending" state was delivered in v11.5.4.0.

    Further work to improve ALTER TABLE operations is under consideration:

    * DB24LUW-I-1097: increasing the number of units of work containing REORG-recommended operations before a full offline reorg must be performed

    * DB24LUW-I-1098: increasing the number of ALTER TABLE operations that can be performed online without placing the table in "reorg pending" state

    This will provide database administratosr with more flexibility and ability to avoid outages.

  • Guest
    Dec 2, 2020

    What version and or fixpack has this been delivered ? From my understanding tables would still go into REORG pending state with certain alter statements.

    I am aware of DB2_BLOCK_REORG_PENDING state registry variable which will prevent the DBA from performing operations that will put the table into REORG pending state but that does not mean that there is a way to perform these operations with out large tables going into REORG pending state if we indeed perform those operations.

    Am I missing something ?