Restrictions on range-clustered tables

There are contexts in which range-clustered tables cannot be used, and there are certain utilities that cannot operate on range-clustered tables.

The following restrictions apply to range-clustered tables:
  • Range-clustered tables cannot be specified in a Db2 pureScale® environment (SQLSTATE 42997).
  • Partitioned tables cannot be range-clustered tables.
  • Declared temporary tables and created temporary tables cannot be range-clustered tables.
  • Automatic summary tables (AST) cannot be range-clustered tables.
  • The load utility is not supported. Data can be inserted into a range-clustered table through the import utility or through a parallel insert application.
  • The REORG utility is not supported. Range-clustered tables that are defined with the DISALLOW OVERFLOW option do not need to be reorganized. Range-clustered tables that are defined with the ALLOW OVERFLOW option cannot have the data in this overflow region reorganized.
  • The DISALLOW OVERFLOW clause on the CREATE TABLE statement cannot be specified if the table is a range-clustered materialized query table.
  • The design advisor will not recommend range-clustered tables.
  • Multidimensional clustering and clustering indexes are incompatible with range-clustered tables.
  • Value and default compression are not supported.
  • Reverse scans on range-clustered tables are not supported.
  • The REPLACE parameter on the IMPORT command is not supported.
  • The WITH EMPTY TABLE option on the ALTER TABLE...ACTIVATE NOT LOGGED INITIALLY statement is not supported.