This topic describes the limitations on data migration and synchronization features of OceanBase Migration Service (OMS).
Supported database versions
The following tables list the supported versions of OceanBase Database for data migration and synchronization.
For OceanBase Database of a version earlier than V4.x, the current OMS version supports pulling full data and incremental data from OceanBase Database as the source and writing data to OceanBase Database as the destination.
For OceanBase Database V4.x, the current OMS version supports pulling full data from OceanBase Database as the source and writing data to OceanBase Database as the destination.
For incremental data synchronization to OceanBase Database V4.x, the following versions are supported. For other versions, you need to perform a hot store version upgrade to enable incremental data synchronization.
V4.1.x
V4.2.1.9, V4.2.2.1, V4.2.3.0, V4.2.4.0, V4.2.5.0, V4.3.0.1, V4.3.1.0, V4.3.2.1, V4.3.3.1
The following tables also list the supported versions of databases other than OceanBase Database and OCP for data migration and synchronization.
| Feature | Other database versions | OCP versions |
|---|---|---|
| Data migration |
|
|
| Data synchronization |
|
|
Supported system architectures
OMS supports the x86 and ARM architectures.
Notice
The ARM architecture is not supported for the following scenarios:
Incremental synchronization from a DB2 LUW database to an Oracle-compatible tenant of OceanBase Database
Incremental synchronization from an Oracle-compatible tenant of OceanBase Database to a DB2 LUW database
Incremental synchronization from a DB2 LUW database to a MySQL-compatible tenant of OceanBase Database
Incremental synchronization from a MySQL-compatible tenant of OceanBase Database to a DB2 LUW database