Migrating from MySQL to OceanBase works well for ANSI SQL workloads. Plan extra time for auto-increment semantics, charset collations, and stored procedure compatibility.

Phase 1: Discovery

  1. Inventory schemas, row counts, and peak QPS/TPS.
  2. Run OMA (OceanBase Migration Assessment) against source dumps.
  3. Flag incompatible DDL: FULLTEXT, certain JSON functions, and engine-specific hints.

Phase 2: Schema conversion

Convert DDL with OMA or manual review. Replace ENGINE=InnoDB clauses. Validate index coverage on converted tables before data load.

Phase 3: Data sync

Use OMS (OceanBase Migration Service) for incremental CDC. Maintain a replication lag dashboard; target < 5s before cutover window.

Phase 4: Cutover

  1. Freeze writes on source (or enable read-only).
  2. Wait for OMS lag = 0.
  3. Run row-count and checksum validation queries.
  4. Point applications to OBProxy endpoint.
  5. Keep rollback DNS for 24 to 48 hours.