Eliminating unnecessary partitioning indexes

You can reclaim the space used by partitioning indexes by converting to table-controlled partitioning. A partitioning index requires as many data sets as the partitioned table space.

About this task

In table-controlled partitioning, partitioning key and limit keys are specified in the CREATE TABLESPACE statement and not the CREATE INDEX statement, which eliminates the need for any partitioning index data sets.

Learn more: For comprehensive background, how-to information, and examples for various paths for converting your deprecated classic partitioned (non-UTS) table spaces to partition-by-range table spaces, see the white paper Conversion from index-controlled partitioning to Universal Table Space (UTS).

Procedure

To eliminate the disk space that is required for the partitioning index data sets:

  1. Convert the table to a partition-by-range table space as described in Converting partitioned (non-UTS) table spaces to partition-by-range universal table spaces.
  2. Drop indexes that are used solely to partition data and not to access it.