Partition-by-growth (UTS) table spaces
With partition-by-growth (UTS) table spaces you can partition according to data growth, which enables segmented tables to be partitioned as they grow, without the need for key ranges.
Partition-by-growth (UTS) table spaces are universal table spaces that can hold a single table. The space in a partition-by-growth (UTS) table space is divided into separate partitions. Partition-by-growth table spaces are best used when a table is expected to exceed 64 GB and does not have a suitable partitioning key for the table.
Partition-by-growth (UTS) table spaces are like single-table DB2®-managed segmented table spaces. DB2 manages partition-by-growth table spaces and automatically adds a new partition when more space is needed to satisfy an insert. The table space begins as a single-partition table space and automatically grows, as needed, as more partitions are added to accommodate data growth. Partition-by-growth table spaces can grow up to 128 TB. The maximum size is determined by the MAXPARTITIONS and DSSIZE values that you specified and the page size.
Although a partition-by-growth table space is partitioned, it has segmented organization and segmented space management capabilities within each partition. Unlike a non-segmented structure, the segmented structure provides better space management and mass delete capabilities. The partitioning structure allows DB2 utilities to continue partition-level operations and parallelism capabilities.
- The PART option of the LOAD utility is not supported.
- The REBALANCE option of the REORG utility is not supported.
- The default SEGSIZE value 32.
- Table spaces must be DB2-managed (not user-managed) so that DB2 has the freedom to create data sets as partitions become full.
- Partitions cannot be explicitly added, rotated, or altered. Therefore, ALTER TABLE ROTATE PARTITION and ALTER TABLE ALTER PARTITION statements cannot target a partition of a partition-by-growth table space.
- XML spaces are always implicitly defined by DB2.
- A non-partitioning index (NPI) always uses a 5 byte record identifier (RID).
- Partitioned indexes are not supported.