OceanBase Migration Service (OMS) V2.1.0 allows you to synchronize data from an OceanBase or Sybase ASE database to a RocketMQ instance, and supports user management and easy-to-use migration and synchronization features.
Version information
Version number: V2.1.0
Previous version: V2.0.0
Version release date: January 25, 2021
Compatible database versions
| Feature | OceanBase database versions | Other database versions |
|---|---|---|
| Data migration | V1.4.79, V2.1.1, V2.2.20, V2.2.30, V2.2.50, V2.2.52, V2.2.70, V2.2.72, V2.2.74, and V2.2.75 |
|
| Data synchronization | V2.2.20, V2.2.30, V2.2.50, V2.2.52, V2.2.70, V2.2.72, V2.2.74, and V2.2.75 |
|
New features
Data synchronization
Allows you to synchronize incremental data from an Oracle-compatible or MySQL-compatible tenant of OceanBase Database to a RocketMQ instance.
Allows you to synchronize incremental data from a Sybase ASE 12.5 database to a RocketMQ instance.
User management
Improves user login, user logout, user creation, personal information, role, and privilege management to ensure the security of data links.
Easier-to-use migration and synchronization management
Dynamically displays the delay of the current incremental timestamp and real-time traffic information of data migration and synchronization projects, and allows you to view the synchronization performance variation curve by section.
Allows you to specify a data pulling timestamp for consuming data again in a data synchronization project.
Allows you to edit the synchronization objects of the current data synchronization project, for example, add or delete tables to be synchronized.
Allows you to specify whether to synchronize data of an OceanBase database in strict accordance with the order of SQL statements.
Displays richer configuration information about data synchronization projects, such as the start timestamp, topics, sharding columns, and tenant of the cluster to which the synchronization objects belong.
Synchronizes backend alerts of monitoring events to OceanBase Cloud Platform (OCP), such as the delay of data migration and synchronization projects as well as system faults.
Limits
Data migration
Take note of the following limits when you migrate data from a MySQL database in a data migration project:
Full or incremental migration of tables without a primary key (PK) is not supported.
Only the MySQL InnoDB storage engine is supported.
Automatic synchronization of DDL statements is not supported during incremental migration.
Data synchronization
Real-time synchronization is not supported for tables without a PK in MySQL-compatible tenants of OceanBase Database.
Real-time synchronization is not supported for tables without a PK and partitioned tables of a Sybase database. A total of 13 data types are supported in incremental parsing, namely, CHAR, NUMERIC, INT, DATETIME, VARCHAR, DECIMAL, SMALLINT, TINYINT, BIT, BINARY, REAL, NVARCHAR, and FLOAT.
For a project for migrating data from a Sybase database to a RocketMQ instance, real-time timestamps cannot be displayed on the OMS console.
We recommend that a maximum of 2000 data tables be synchronized in a single project, and that the size of a single message synchronized to a RocketMQ instance do not exceed 4 MB.
You cannot create projects to synchronize data from an OceanBase database to Kafka or RocketMQ instances that only differ in the capitalization of topic names.
If you have upgraded OMS from V2.0.0 to V2.1.0, you cannot modify the synchronization objects in the synchronization projects created in OMS V2.0.0.
HA
After OMS V2.1.0 is deployed, the high availability (HA) service is disabled by default. You can enable HA based on your business requirements.