Version information variables
Version: V4.2.0
Previous version: V4.1.0
Release date: August 17, 2023
Upgrade path:
OceanBase Migration Service (OMS) of a version earlier than V3.2.1 must be upgraded to V3.2.1 first.
OMS V3.2.1 and later can be directly upgraded to OMS V4.2.0.
Recommended oblogproxy version: V2.1.0 and later
Compatible database versions
| Feature | OceanBase Database version | Other database version | OCP version |
|---|---|---|---|
| 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, 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, V4.0.0, V4.1.0, and V4.2.0 |
|
|
| Data synchronization | 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, V3.2.4, V4.0.0, V4.1.0, and V4.2.0 |
|
|
New features
OMS V4.2.0 supports OceanBase Database V4.2.0
Data migration
The reverse incremental migration feature supports data backflow after you migrate data from homogeneous or heterogeneous databases such as Oracle, OceanBase, TiDB, and PostgreSQL databases to OceanBase Database V4.2.0.
OMS V4.2.0 supports OceanBase Database V4.2.0 as the source for data migration.
OMS V4.2.0 supports data migration between tenants of OceanBase Database V4.2.0 and from OceanBase Database V4.2.0 to MySQL, Oracle, and DB2 LUW databases.
Data synchronization
- OMS V4.2.0 supports OceanBase Database V4.2.0 as the source for data synchronization. You can synchronize data from OceanBase Database V4.2.0 to Kafka, DataHub, and RocketMQ instances.
OMS V4.2.0 allows you to check archived logs in OceanBase Database V4.x
In OceanBase Database V4.x and later versions, OMS V4.2.0 can consume archived logs for incremental synchronization if clogs are recycled. This further reduces the risk that a project is interrupted by log recycling and must be re-created.
OMS V4.2.0 supports the check on the enabling status of log archiving for OceanBase Database V4.x during reverse incremental synchronization from or to OceanBase Database V4.x. This precheck item prompts you to enable log archiving to improve project stability.
Fixed issues
| Issue | Introduced in |
|---|---|
| During data migration from an Oracle database to an Oracle tenant of OceanBase Database, forward switchover fails due to the ENABLE NOVALIDATE attribute in the constraint. | This issue has existed since the earliest version. |
During the creation of a data migration project from an Oracle database to a MySQL tenant of OceanBase Database, the document content is not displayed after View Issue is clicked. |
OMS V4.1.0 |
Known issues
| Issue | Introduced in | Solution |
|---|---|---|
During full data migration from a MySQL database to a MySQL tenant of OceanBase Database, the data in the source database still overwrites the data in the destination database even if the Ignore option is selected. |
OMS V4.0.1 | None |