OceanBase Migration Service (OMS) supports the real-time synchronization between a MySQL-compatible or Oracle-compatible tenant of OceanBase Database and a Kafka, RocketMQ, or DataHub data source. It also allows you to synchronize data from other types of databases to a RocketMQ database and from ODP/IDB logical tables to physical tables in a MySQL-compatible tenant of OceanBase Database or to a DataHub instance. OMS is suitable for real-time data warehouse construction, data query, report distribution, and other business scenarios.
Supported synchronization operations
In the following table, OB_MySQL stands for a MySQL-compatible tenant of OceanBase Database, and OB_Oracle stands for an Oracle-compatible tenant of OceanBase Database. For more information about DDL operations supported in incremental synchronization, see corresponding topics about data synchronization tasks.
| Data synchronization task | Schema synchronization | Full synchronization | Incremental synchronization of DML operations | Incremental synchronization of DDL operations | Table without a primary key |
|---|---|---|---|---|---|
| OB_MySQL -> Kafka | Supported | Supported | Supported | Supported | Not supported |
| OB_MySQL -> RocketMQ | Not supported | Supported | Supported | Not supported | Not supported |
| OB_MySQL -> DataHub (Tuple type) | Supported | Supported | Supported | Not supported | Not supported |
| OB_MySQL -> DataHub (Blob type) | Supported | Supported | Supported | Supported | Not supported |
| OB_Oracle -> Kafka | Supported | Supported | Supported | Supported | Not supported |
| OB_Oracle -> RocketMQ | Not supported | Supported | Supported | Not supported | Not supported |
| OB_Oracle -> DataHub (Tuple type) | Supported | Supported | Supported | Not supported | Not supported |
| OB_Oracle -> DataHub (Blob type) | Supported | Supported | Supported | Supported | Not supported |
| Oracle -> DataHub (Tuple type) | Supported | Not supported | Supported | Not supported | Not supported |
| Oracle -> DataHub (Blob type) | Supported | Not supported | Supported | Not supported | Not supported |
| MySQL -> DataHub (Tuple type) | Supported | Not supported | Supported | Not supported | Not supported |
| MySQL -> DataHub (Blob type) | Supported | Not supported | Supported | Not supported | Not supported |
| ODP -> DataHub (Tuple type) | Supported | Supported | Supported | Not supported | Not supported |
| ODP -> DataHub (Blob type) | Supported | Supported | Supported | Supported | Not supported |
| IDB -> DataHub (Tuple type) | Supported | Supported | Supported | Not supported | Not supported |
| IDB -> DataHub (Blob type) | Supported | Supported | Supported | Supported | Not supported |
| ODP -> OB_MySQL | Not supported | Supported | Supported | Supported | Not supported |
| IDB -> OB_MySQL | Not supported | Supported | Supported | Supported | Not supported |
Supported task types
Data synchronization tasks from the source to the destination mainly support incremental data synchronization scenarios, that is, real-time writes of DML changes from the source to the destination. The minimum synchronization granularity supported by OMS is the table level, and the maximum is the tenant level.
OMS provides data synchronization functionality and supports the following task types: