All Products
Search
Document Center

ApsaraDB for OceanBase:Drop subpartitions

Last Updated:Mar 17, 2023

This topic describes the supported conversion scope of ALTER TABLE DDL operations for dropping subpartitions during data migration from an Oracle database to an Oracle tenant of OceanBase Database.

Syntax

drop_table_subpartition:
DROP subpartition_extended_names
  [ update_index_clauses [ parallel_clause ] ]

subpartition_extended_names:
{ SUBPARTITION | SUBPARTITIONS }
subpartition | { FOR ( subpartition_key_value [, subpartition_key_value ]... ) }
  [, subpartition | { FOR ( subpartition_key_value [, subpartition_key_value ]... ) } ]...

Supported operations

  • Dropping a subpartition by specifying the subpartition name is supported. Sample code:

    ALTER TABLE T DROP SUBPARTITION SP0,SP1
    ALTER TABLE T DROP SUBPARTITIONS SP0,SP1
  • Updating indexes in a table by using the UPDATE GLOBAL INDEXES clause is supported.

Unsupported operations

  • Dropping a subpartition by specifying the subpartition key value is not supported.

  • Invalidating global indexes by using the INVALIDATE GLOBAL INDEXES clause is not supported. This clause will be converted into the UPDATE GLOBAL INDEXES clause.

Ignored clauses and options

Note

The following clauses and options will be ignored and will not be resolved or converted when they are specified in the synchronized DDL statements.

  • The update_all_indexes_clause clause for updating indexes in a table.

  • The parallel_clause clause for modifying the default query and DML parallelism for a table.