Composite partitioning

This topic describes the conversion scope of CREATE TABLE DDL operations for defining composite partitions during data migration from an Oracle database to an Oracle-compatible tenant of OceanBase Database.

RANGE composite partitioning

Syntax of composite_range_partitions:

PARTITION BY RANGE ( column [, column]... )
  [ INTERVAL ( expr ) [ STORE IN ( tablespace [, tablespace]... ) ]]
  { subpartition_by_range
  | subpartition_by_list
  | subpartition_by_hash
  }
( range_partition_desc [, range_partition_desc ]... )

• Defining a partition as a RANGE partition is supported. For more information, see RANGE partitioning. Defining RANGE, LIST, and HASH subpartitions by using the subpartition_by_range, subpartition_by_list, and subpartition_by_hash options is supported. For more information, see Subpartitioning.

• Defining RANGE partitions by using the range_partition_desc option is supported. For more information, see User-defined partitions.

• Specifying partition intervals and namespaces by using the INTERVAL and STORE IN options is not supported. These options will be ignored.

LIST composite partitioning

Syntax of composite_list_partitions:

PARTITION BY LIST ( column [, column]... )
[ AUTOMATIC [ STORE IN ( tablespace [, tablespace ]... ) ] ]
  { subpartition_by_range
  | subpartition_by_list
  | subpartition_by_hash
  }
( list_partition_desc [, list_partition_desc]... )

• Defining a partition as a LIST partition is supported. For more information, see LIST partitioning. Defining RANGE, LIST, and HASH subpartitions by using the subpartition_by_range, subpartition_by_list, and subpartition_by_hash options is supported. For more information, see Subpartitioning.

• Defining LIST partitions by using the list_partition_desc option is supported. For more information, see User-defined partitions.

• Automatically creating LIST partitions and specifying tablespaces by using the AUTOMATIC and STORE IN options are not supported. These options will be ignored.

HASH composite partitioning

Syntax of composite_hash_partitions:

PARTITION BY HASH (column [, column ] ...)
{ subpartition_by_range
| subpartition_by_list
| subpartition_by_hash
}
{ individual_hash_partitions
| hash_partitions_by_quantity
}

Defining a partition as a HASH partition is supported. For more information, see HASH partitioning. Defining RANGE, LIST, and HASH subpartitions by using the subpartition_by_range, subpartition_by_list, and subpartition_by_hash options is supported. For more information, see Subpartitioning.