A table can become fragmented due to many updates, causing performance to deteriorate. If you collected statistics and did not notice a visible performance improvement, reorganizing table data may help. When you reorganize table data you are rearranging the data of a table into a physical sequence according to a specified index, and removing the free space that is inherent in fragmented data. This can provide faster access to the data and thereby improve performance.
Before you reorganize tables, we recommend you collect the statistics of the data to allow the reorgchk command to see up-to-date statistics. This is described in "Step 4. Collecting Statistics". The results of the reorgchk command will help you determine whether a reorganization of table data should be performed. The reorgchk command has an option to cause statistics to be collected as part of its processing. See the Command Reference for information on this command.
To reorganize table data:
The value is initially <none>, specifying that the temporary copy should be stored in the table space where the table currently resides.
If you specify <none> (the default), the table rows are reorganized without regard to order.
You should re-bind application programs that use static SQL after collecting statistics, because the SQL optimizer may choose a different access plan given the new statistics. In particular, you should re-bind those programs that reference tables for which new statistics are available. See the Quick Beginnings for your platform for instructions on binding application programs.
The Administration Guide provides more details about reorganizing table data and collecting statistics.