This topic introduces the DDL statements supported for synchronization between MySQL-compatible tenants of OceanBase Database.
Notice
If an index created in the source table already exists in the target table, the data migration service automatically ignores the index without interrupting the synchronization process.
Supported DDL statements
ALTER TABLE ADD COLUMNALTER TABLE MODIFY COLUMNNotice
You can increase the column length, but you cannot modify the column type.
ALTER TABLE ALTER COLUMN SET DEFAULTandALTER TABLE ALTER COLUMN DROP DEFAULTALTER TABLE DROP COLUMNCREATE TABLENotice
CREATE TABLE AS SELECTis not supported.DROP TABLETRUNCATE TABLECREATE INDEXandALTER TABLE ADD INDEXDROP INDEXandALTER TABLE DROP INDEXRENAME TABLEandALTER TABLE RENAME
Limitations
If the tables to be synchronized involve unsupported DDL statements, the migration task may be interrupted, resulting in unrecoverable data inconsistencies.
Frequent DDL operations on a single table are not supported. Perform the next DDL operation only after the Store has completed the current operation based on the log position. Otherwise, the Store may exit unexpectedly or cause unrecoverable data errors.
Ensure that no DDL operations are performed for a period before you create a Store or while the Store is starting. If logs need to be pulled from an earlier point, ensure that no DDL operations are performed between the log pull point and the current time. Otherwise, the Store may exit unexpectedly or cause unrecoverable data errors.
The table names before and after the
RENAME TABLEoperation must be present in the list of tables to be synchronized.
