
Converting partitioned (non-UTS) table spaces to partition-by-range universal table spaces
You can convert existing partitioned (non-UTS) table spaces, which are deprecated, to partition-by-range table spaces.
Before you begin

For more information about currently committed data access, see Accessing currently committed data to avoid lock contention.

About this task
Partition-by-range table spaces are preferred over deprecated partitioned (non-UTS) tables spaces because the segmented structure of partition-by-range table spaces improves space management and faster performance for mass-deletes. Also, some capabilities introduced in DB2® 9 and later releases are supported for partition-by-range table spaces but not for partitioned (non-UTS) tables spaces, such as:
FL 502 Defining or altering key labels for z/OS® DFSMS data set encryption
Relative page numbering
Inserting partitions
- Dropping columns
- Altering the COMPRESS attribute of a table space
- Altering the DSSIZE value
- Altering the MEMBER CLUSTER attribute of a table space
- Altering the buffer pool page size for a table space
- Inline LOBs
- Clone tables
- Altering the compression attribute of an index as a pending definition change
- Altering the buffer pool page size of an index as a pending definition change

classicpartitioned (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 convert a partitioned (non-UTS) table space to a partition-by-range table space, complete the following steps:
