Supported DDL operations in incremental migration
CREATE TABLEYou can create partitioned tables but cannot use
CREATE TABLE AS SELECTto create tables.DROP TABLETRUNCATE TABLEADD PARTITIONYou can add partitions and subpartitions by using RANGE or LIST partitioning. HASH partitioning is not supported.
DROP PARTITIONYou can drop one or more partitions and subpartitions.
TRUNCATE PARTITIONYou can truncate one or more partitions and subpartitions.
RENAME TABLEandALTER TABLE RENAMEALTER TABLE ADD COLUMNALTER TABLE MODIFY COLUMNNotice
You can only extend the column length. You cannot modify the column type.
ALTER TABLE DROP COLUMNCREATE INDEXDROP INDEXAdding comments to tables or columns
Limits of DDL operations in incremental migration
If a table to be synchronized involves DDL operations that are not supported, the migration link may be interrupted and unrecoverable data exceptions may be caused.
Frequent DDL operations on a table are not supported. After the store finishes a DDL operation, which can be determined based on the timestamp, it proceeds to the next DDL operation. Otherwise, the store may exit unexpectedly or cause unrecoverable data exceptions.
Make sure that no DDL operations are performed before you create a store and when a store is being started. If log pulling is involved, make sure that no DDL operations are performed during the period from the start time when logs are pulled to the current time. Otherwise, the store may exit unexpectedly or cause unrecoverable data exceptions.
The table names before and after the
RENAME TABLEstatement must be both included or both not included in the list of tables to be synchronized.If you delete an unnamed primary key, the corresponding constraint whose name starts with
SYS_Cin the Oracle database is deleted. If you perform inter-database data migration or synchronization, for example, from an Oracle database to an OceanBase database, the primary keys in the OceanBase database cannot be deleted because they are different from those in the Oracle database.A table creation DDL operation that involves the
CASE WHEN INDEXclause cannot be synchronized.If you enable DDL operations in incremental migration, the
DROP INDEXstatement is executed on all indexes, which may cause index loss in the destination database.