This topic describes the limits of the data migration and data synchronization features of OceanBase Migration Service (OMS).
The following table describes the versions of OceanBase Database and other database services and terminals that support data synchronization and data migration:
Category Data migration Data synchronization OceanBase Database V1.4.79, V2.1.1, V2.2.20, V2.2.30, V2.2.50, V2.2.52, V2.2.70,V 2.2.72, V2.2.74, V2.2.75, V2.2.76, V2.2.76BP1, V2.2.77, V3.1.0, V3.1.1, V3.1.2, V3.2.1, V3.2.2, V3.2.3, V3.2.4, and V4.0.0
Notice:
OceanBase Database V1.x can be configured only as the destination and does not support forward switchover when it serves as the destination.V2.2.20, V2.2.30, V2.2.50, V2.2.52, V2.2.70, V2.2.72, V2.2.74, V2.2.75, V2.2.76, V2.2.76BP1, V2.2.77, V3.1.0, V3.1.1, V3.1.2, V3.2.1, V3.2.2, V3.2.3, and V3.2.4 Other database services and terminals - MySQL: 5.5, 5.6, 5.7, and 8.0
- MariaDB: V10.2
- DB2 LUW: V10.1, V10.5, V11.1, and V11.5
- Oracle Database: 10g, 11g, 12c, 18c, and 19C
Notice:- Oracle Database 12c and later support container databases (CDBs) and pluggable databases (PDBs).
- OMS does not support data migration from Oracle Database 10g to an OceanBase database in MySQL tenant mode.
- PostgreSQL: V10.x
- Kafka:0.9, 1.0, and 2.x
- RocketMQ: V4.x and V5.x
- Oracle Database: 10g, 11g, 12c, 18c, and 19C
- MySQL: V5.5、V5.6、V5.7、V8.0
We recommend that you use the following versions of OceanBase Cloud Platform (OCP):
V2.x: V2.3.9、V2.4.5、V2.5.0
V3.x
V4.x
OMS supports the x86 and Arm architectures.
Notice
The Arm architecture does not support the following migration modes:
Incremental synchronization from a DB2 LUW database to an OceanBase database in Oracle tenant mode
Reverse incremental migration from an OceanBase database in Oracle tenant mode to a DB2 LUW database
Incremental synchronization from a DB2 LUW database to an OceanBase database in MySQL tenant mode
Reverse incremental migration from an OceanBase database in MySQL tenant mode to a DB2 LUW database