I am seeking some clarity to further my understanding of the
AREO* or AREOR advisory status after the a reorg.
After performing an ALTER TABLE to increase a column size (CHAR data type), the corresponding TS goes to a AREO* advisory status.
Now, as per the manual, it mentions the difference between the AREO* or AREOR advisory status.
REORG-pending (AREO*) advisory status:
Indicates that the object needs to be reorganized for optimal performance. AREO* status can be reset on a single partition, regardless of whether adjacent partitions are also in AREO* status. The affected objects are not restricted and can be accessed by both readers and writers.
REORG-pending (AREOR) advisory status:
Indicates that the object should be reorganized to apply pending definition changes. AREOR status must be reset for all adjacent logical partitions that are in AREOR status. The affected objects are not restricted and can be accessed by both readers and writers. The affected objects are not modified until the REORG job that materializes the definition changes is run.
My understanding of the status description is that if the status
is AREO*, it suggests the COLUMN size has been altered and in
effect allow an INSERT of data of the increased column size.
And that the reorg is desirable for performance reasons.
Since I am working on an ALTER a fairly large table, there is a small chance that the REORG may not complete in the available maintenance window. So, I am looking for some comfort that even if the reorg does not go through, the application can still use the increased column size (of the Altered table). Is my understanding of the AREO* advisory status correct? or is there something more I need to know before I am comfortable with the fact that the reorg is a nice to have as opposed to must have.