Reorganization processing can be performed on an entire table; this is the method that is usually used. Reorganization by table is executed when the results of executing the database condition analysis utility indicate that the entire table needs to be reorganized. The following figure illustrates reorganization of an entire table.

Figure 13-2 Reorganization of an entire table

Note: The data indicated by shading is subject to reorganization.

Explanation

The table to be reorganized is specified in the -t option of the database reorganization utility.

Reorganization by RDAREA reorganizes the RDAREAs in which the table is stored. This method can be used only on tables that are row-partitioned. Reorganization of RDAREAs is executed when the results of the database condition analysis utility indicate that to reorganizing only a portion of a row-partitioned table would suffice. This reduces the processing time compared with reorganization of the entire table. The following figure illustrates reorganization of an RDAREA.

Figure 13-3 Reorganization of an RDAREA

Note: The data indicated by shading is subject to reorganization.

Explanation

The table to be reorganized is specified in the -t option and the RDAREAs to be reorganized are specified in the -r option of the database reorganization utility.

Reference note

If an RDAREA satisfying all of the conditions listed below is reorganized by RDAREA, a non-partitioning key index will not be created. To create a non-partitioning key index, the database reorganization utility (re-creating an index) must be executed again.

• The table to be reorganized has row partitioning within a server.
• A non-partitioning key index is defined for the table to be reorganized.
• The non-partitioning key index is not row-partitioned.

The following figure shows an example in which a non-partitioning key index is not created during reorganization by RDAREA.

Figure 13-4 Example in which a non-partitioning key index is not created during reorganization by RDAREA

Explanation

Even though reorganization by RDAREA is applied to RDAREA1, a non-partitioning key index is not created. Index information will simply be output to an index information file. To create a non-partitioning key index, the index must be re-created with the database reorganization utility. Thus, we recommend that you reorganize by table, rather than by RDAREA, in such a case.

This processing reorganizes all tables in a schema in the batch mode. Reorganization by schema can be used when you wish to reorganize all the tables you own on a batch basis. The following figure illustrates reorganization of a schema.

Figure 13-5 Reorganization of a schema

Note: The data indicated by shading is subject to reorganization.

Explanation

The authorization identifier of the schema to be reorganized is specified in the -t option of the database reorganization utility. The specification format is -t authorization-identifier.all.