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.
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "firstname.lastname@example.org" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions