Table partitioning restrictions include the following:

  • Table partitions must reside in Type II areas.
  • Partitions can not span storage areas.
  • A maximum of 32,768 partitions (one of which is the composite initial partition) are allowed per table.
  • A maximum of 15 sub-partitions are allowed per table.
  • Only one range column per table may be specified as defining a range partition; it can be either the only partition or the last sub-partition.
  • Overlapping range partitions are not supported. Ranges are contiguous, without gaps. Data in each range partition is all data less than or equal to (<=) the partition definition value down to the previous partition definition or down to the beginning of time if there is no smaller value.
  • Partition-aligned columns in a local index must be ascending.
  • Once you partition a table, if you need to re-define partitions for that table, you must dump and load the data.
  • Once you enable table partitioning for your database, you must remove all partitions to in order to disable the feature.
  • Table partitioning is not supported for multi-tenant tables.
    Note: Note you can have both multi-tenant and partitioned tables in the same database, but you cannot use both features on the same table.