OMS V4.3.0

Version information

• Version number: V4.3.0

• Previous version: V4.2.5 BP1

• Version release date: May 30, 2025

• Upgrade path:

  • OMS V3.2.1 and earlier versions must be upgraded to V3.2.1 first.

  • OMS V3.2.1 and later versions can be directly upgraded to OMS V4.3.0.

    Note

    Due to underlying component integration, DataHub tasks cannot be displayed after OMS is upgraded from V3.2.1 to a later version. If you want to upgrade OMS from V3.2.1 to a later version with a DataHub task involved, contact OMS Technical Support.

New features

Complex object migration supported

OMS V4.3.0 allows you to migrate stored procedures, functions, triggers, sequences, synonyms, custom types, and packages from an Oracle database to the Oracle compatible mode of OceanBase Database. If a data migration task involves full migration or incremental synchronization, triggers and sequences will be migrated during forward switchover.

Support for incremental data delivered by OGG to Kafka

When you migrate data from an Oracle database to the Oracle compatible mode of OceanBase Database, OMS V4.3.0 allows you to use OGG to deliver incremental data from the Oracle database to Kafka, which enables OMS to obtain incremental data from Kafka for data synchronization.

Compared with the LogMiner-based data delivery method, the OGG-based data delivery method significantly improves stability and reliability and effectively avoids issues such as the loss of transaction data across archives and task interruptions that occur in the LogMiner-based data delivery method. With proper task planning, OMS currently supports incremental data synchronization at a rate of over 200,000 RPS from Oracle databases, which is 3 to 5 times the performance of the LogMiner-based data delivery method.

Download conflict data file

OMS may encounter unique key conflicts when inserting data into the target database in abnormal scenarios, such as when the target database contains data or when data is pulled back during task restart. OMS V4.3.0 reminds you of conflict data and allows you to download a conflict data file to facilitate conflict data analysis and assessment of the impact of conflict data on your business. The file contains the INSERT SQL statements that trigger the conflict data.

Download converted objects

During schema migration, OMS migrates the source schema to the target database by converting the source schema objects. OMS V4.3.0 allows you to download the converted objects and their converted content so that you can analyze the impact on your business and decide whether to modify the schema objects.

Support for tables without non-null unique keys

Data migration and synchronization tasks are no longer restricted on tables without non-null unique keys, except for data migration and synchronization from Oracle/MySQL/ODP/IDB database to DataHub or from ODP/IDB database to the MySQL compatible mode of OceanBase Database. Tables without non-null unique keys can be migrated or synchronized normally. For tasks that support hidden columns Hidden column mechanism, the console provides an option that allows you to choose whether to configure hidden columns to ensure the consistency of table migration and synchronization.

Ease-of-use improvements

• For hidden columns created in OMS, support automatic switching of comments between Chinese and English based on the language settings of the deployment environment.

• When synchronizing data from OceanBase Database to Kafka, support configuring the case sensitivity of object names in Kafka messages.

• Optimize the object selection logic so that if a task does not involve full or incremental synchronization steps, it no longer requires the task to include table objects.

• When importing CSV objects, no longer require that the objects must exist at the source. If they do not exist, support their batch removal during schema migration or full migration.

• Support configuring automatically enter the next stage upon completion for schema migration, and allow manual adjustment of object schemas after schema migration.

• Modify the options for index migration mode and add support for not migrating normal indexes.

Bug fixes

• Fixed the issue where the parameter configuration feature does not take effect for non-shared Store components.

OpenAPI

• Added an OpenAPI for resetting the timestamp of incremental synchronization and reverse incremental synchronization. For more information, see ResetIncrStartTimestamp.

Feature matrix

Data migration

Data synchronization

Database versions supported

The following table describes the database versions of OceanBase Database that are supported by the current OMS release.

• For OceanBase Database earlier than V4.x, the current OMS release supports OceanBase Database as the source to pull full and incremental data and as the target to write data.

• For OceanBase Database V4.x, the current OMS release supports OceanBase Database as the source to pull full data and as the target to write data.

• For incremental synchronization of OceanBase Database V4.x, only the following versions are supported. For other versions, you need to perform a hot store version upgrade.

  • V4.1.x

  • V4.2.1.11, V4.2.2.1, V4.2.3.0, V4.2.4.0, V4.2.5.3, V4.3.0.1, V4.3.1.0, V4.3.2.1, V4.3.3.1, V4.3.4.1, and V4.3.5.2 (and earlier versions)

The following table describes the database versions and OceanBase Cloud Platform (OCP) versions that are supported by the data migration and synchronization feature.