OMS V4.3.1

Version information

• Version: V4.3.1

• Previous version: V4.3.0 BP3

• Release date: October 9, 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.1.

    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

Extended data migration task capabilities

OMS V4.3.1 supports migrating data from a PostgreSQL database to an Oracle-compatible OceanBase Database. This feature enables structural migration, full migration, incremental synchronization, reverse incremental migration, full verification, and row verification from a PostgreSQL database to an Oracle-compatible OceanBase Database. Additionally, it extends the capability to migrate data from a PostgreSQL database to a MySQL-compatible OceanBase Database, supporting DDL synchronization, modification of matching rules, and dynamic addition of objects for incremental synchronization or reverse incremental migration. This helps users migrate the structure and data from a PostgreSQL database to an OceanBase Database more conveniently.

Support for bidirectional synchronization tasks

When creating a data migration task from a MySQL, Oracle, or OceanBase Database to an OceanBase Database, users can choose to create either a unidirectional or bidirectional synchronization task based on their requirements. If they choose to create a bidirectional synchronization task, they can configure the reverse task when the forward task enters incremental synchronization mode. This allows for automatic configuration of bidirectional replication loops, facilitating scenarios such as gray-scale switching and bidirectional parallel running.

New data verification capabilities

OMS V4.3.1 separates data verification from the data migration process, allowing users to configure data verification tasks independently. This provides greater flexibility in operations. All data verification tasks now support row verification, enabling users to quickly verify data by comparing the number of rows in tables. Additionally, incremental verification capabilities are supported for tasks involving Oracle <-> OB_Oracle, MySQL <-> OB_MySQL, OB_MySQL -> OB_MySQL, and OB_Oracle -> OB_Oracle. This allows for rapid comparison of incremental changes between the source and destination, significantly reducing the time required for full verification in large-scale data scenarios and shortening the verification window during cutover.

Column selection and mapping capabilities

OMS V4.3.1 allows users to select specific columns for synchronization or verification within a task. It also supports renaming column names to establish mapping relationships between the source and destination. This feature enables users to synchronize or verify specific columns even when the structures of the source and destination are not fully aligned.

Kafka data source support for mutual TLS authentication

OMS V4.3.1 introduces support for mutual TLS (mTLS) authentication in Kafka data sources, meeting higher security requirements for data sources.

Partition-level migration and verification

OMS V4.3.1 allows users to select specific partitions for migration or verification during full data migration or full data verification. This enables partial data migration or verification, meeting the need for quick data migration or verification after business validation.

Support for Chinese object names

OMS V4.3.1 supports migrating, synchronizing, or verifying tables and columns with Chinese names, meeting the business requirements for Chinese object names in domestic systems.

Extended message format capabilities

• The default JSON format now includes a nanos field under allMetaData, representing nanosecond-level timestamps. This field, when combined with the original timestamp, forms a complete timestamp that includes nanosecond data.

• The Canal JSON format has been updated to correct the last three digits of the es field, allowing it to accurately represent millisecond-level timestamps.

• The Canal JSON format now supports extended fields that can be enabled in the component parameter metaExtend. These fields allow for the extension of transId (transaction ID) and opseqno (operation sequence number within a transaction).

• The INSERT type in Debezium JSON messages now includes a "before": null field, enhancing compatibility with the Debezium JSON message format.

• OGG-compliant message formats are now supported. Users can enable this format by setting the component parameter serializerType to OGG_JSON, enhancing compatibility with the Oracle GoldenGate JSON specification.

Extended OpenAPI

• A new OpenAPI, DescribeRegions, is available for viewing region lists.

• The CreateProject OpenAPI for task creation now includes an interactiveMode parameter, allowing users to choose whether to manually advance task steps.

• A new OpenAPI, AdvanceProject, is available for manually advancing tasks.

• Task-related OpenAPIs now support managing newly added data verification tasks.

Ease-of-use improvements

• When you perform incremental synchronization to synchronize data to the downstream database, the system filters out additional hidden columns created by OMS structure migration by default. This prevents data synchronization failures caused by the absence of these additional hidden columns in the downstream database.

• The SQL performance is optimized when you query non-nullable unique key tables in an Oracle source database. This prevents task exceptions caused by excessively long query durations.

• The migration order of different object types in Oracle structure migration is optimized. This reduces the probability of migration failures caused by object dependencies between different object types.

• You can configure the system parameter datasource.permission.method.root_admin to enable root/admin users to share data sources created by them with ordinary users.

• The logic of DML/DDL statistics in incremental synchronization is added.

• The Oracle Store component returns an error code to warn you of potential data quality risks caused by the closure of some threads on RAC nodes.

Feature matrix of the current version

Data migration

Data synchronization

Data validation

Supported database versions

The following table describes the supported versions of OceanBase Database for data migration and data synchronization.

• For OceanBase Database V4.x and earlier, the current OMS version supports pulling full data + 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 synchronization of OceanBase Database V4.x, only the following versions are supported. Other versions require a hot store version upgrade to be supported.

  • V4.1.x

  • V4.2.1.11, V4.2.2.1, V4.2.3.0, V4.2.4.0, V4.2.5.6, V4.3.0.1, V4.3.1.0, V4.3.2.1, V4.3.3.1, V4.3.4.1, V4.3.5.4, and V4.4.0.1

The following table describes the supported versions of other databases and OceanBase Cloud for data migration and data synchronization.