+20272   TABLE SPACE table-space-name HAS BEEN CONVERTED TO USE TABLE-CONTROLLED PARTITIONING INSTEAD OF INDEX-CONTROLLED PARTITIONING, ADDITIONAL INFORMATION: old-limit-key-value

Explanation

When one of the following statements executed, table-space-name was converted to use table-controlled partitioning instead of index-controlled partitioning:
  • ALTER INDEX with the CLUSTER NO clause
  • ALTER TABLE...ADD PARTITION
  • ALTER TABLE...ALTER PARTITION
  • ALTER TABLE...ROTATE PARTITION
  • CREATE INDEX...ENDING AT without the CLUSTER clause
  • CREATE PARTITIONED INDEX
  • DROP INDEX for a partitioning index

If the statement was ALTER INDEX, CREATE PARTITIONED INDEX, or DROP INDEX, the last partition's old value of old-limit-key-value was set to the highest possible value for an ascending index key column, or the lowest possible value for a descending index key column. For all other statements, *N is returned for old-limit-key-value.

If the statement was ALTER TABLE with the ROTATE PARTITION clause, then certain partitions might be left in REORG pending state.

System action

The statement is successfully executed. If the statement was ALTER INDEX, CREATE PARTITIONED INDEX, or DROP INDEX, the LIMITKEY column in SYSIBM.SYSTABLEPART was set to the highest possible value for an ascending index key column, or the lowest possible value for a descending index key column.

SQLSTATE

01666