OMS V4.3.2

Version information

• Version: V4.3.2

• Previous version: V4.3.1 BP1

• Version release date: January 20, 2026

• Upgrade path:

  • OMS V3.2.1 or earlier: Upgrade to V3.2.1 first.

  • OMS V3.2.1 or later: Upgrade directly to OMS V4.3.2.

    Note

    Due to the integration of underlying components, OMS V3.2.1 does not support DataHub tasks. Therefore, DataHub tasks cannot be displayed after upgrading from V3.2.1. If you upgrade OMS and the upgrade involves DataHub tasks, contact OMS Technical Support.

New features

Data migration and data validation from Milvus to OB_MySQL

OMS now supports data migration and data validation tasks from Milvus to OceanBase Database in MySQL compatible mode. Data migration tasks support schema migration, full migration, incremental synchronization (DML only), and reverse incremental (DML only). Data validation tasks support full validation and row count validation. You can create data migration and data validation tasks from a Milvus database to migrate and verify AI database data to OceanBase Database.

Data migration from OBSharding to OB_MySQL

OMS now supports data migration tasks from OBSharding to OceanBase Database in MySQL compatible mode. These tasks support full migration and incremental synchronization. By retrieving the topology of the OBSharding database, OMS automatically builds data migration tasks between physical databases in OceanBase Database in MySQL compatible mode. This simplifies task creation in OBSharding database migration and synchronization scenarios and improves the ease of use of on-site implementation.

Support for vector types

• PostgreSQL -> OB_MySQL: OMS now supports vector types vector, halfvec, and sparsevec in PostgreSQL to OceanBase Database in MySQL compatible mode. These types are supported in schema migration, full migration, incremental synchronization, and full validation. Vector and halfvec types are converted to the vector type in OceanBase Database, and sparsevec is converted to the sparsevec type in OceanBase Database.

• OB_MySQL -> OB_MySQL: OMS now supports vector types vector, sparsevector, and related vector indexes in OceanBase Database in MySQL compatible mode. These types are supported in schema migration, full migration, incremental synchronization, full validation, and incremental validation.

Support for array types

• PostgreSQL -> OB_MySQL: OMS now supports array types in PostgreSQL to OceanBase Database in MySQL compatible mode. These types are supported in schema migration, full migration, incremental synchronization, and full validation.

• OB_MySQL -> OB_MySQL: OMS now supports array types in OceanBase Database in MySQL compatible mode. These types are supported in schema migration, full migration, incremental synchronization, full validation, and incremental validation.

Extension of support for spatial types

• PostgreSQL -> OB_MySQL/OB_Oracle: OMS now supports native spatial types point and polygon in PostgreSQL to OceanBase Database in MySQL compatible mode and OceanBase Database in Oracle compatible mode. These types are supported in schema migration, full migration, incremental synchronization, and full validation.

Support for new data formats

To ensure that downstream applications do not need to be modified after you switch to OceanBase Database, OMS now supports the OGG_JSON_12X and OGG_JSON data formats, which are used for data format behavior in Oracle GoldenGate for Oracle Database to Kafka. We recommend that you use the OGG_JSON_12X data format for compatibility with OGG V12.x and V19.x and the OGG_JSON data format for compatibility with OGG V21.x and later. For more information, see Data formats.

Stability improvements

• Optimized the processing logic of LOB columns in OMS components based on the design of OBCDC trusted columns. This resolves the issue where the accuracy of data cannot be determined when both the front and rear mirrors of LOB columns are NULL.

• Optimized the issue where a large number of error logs are triggered in OMS due to the generation of a large number of original value updates at the source end when incremental data is obtained from an Oracle database through Kafka.

• Switched the conflict matrix judgment basis of PostgreSQL data migration tasks to the index information on the target end. This avoids the task risk issue caused by incomplete incremental structure information retrieval in the PostgreSQL database.

Performance optimization

• The new batch accumulation feature is added to data migration tasks from Oracle to OB_Oracle. You can configure component parameters to enable batch accumulation for insert and delete operations, thereby improving task performance.

Feature matrix of the current version

Data migration

Data synchronization

Data validation

Supported database versions

The following table lists the supported database versions for data migration and data synchronization.

• For OceanBase Database V4.x, the current OMS version supports full data migration and incremental data synchronization.

• For OceanBase Database V4.x, the current OMS version supports full data migration and data synchronization.

• For OceanBase Database V4.x, the current OMS version supports incremental data synchronization only for the following versions. For other versions, incremental data synchronization is supported only after you upgrade the store version.

  • V4.1.x

  • V4.2.1.11, V4.2.2.1, V4.2.3.0, V4.2.4.0, V4.2.5.7, V4.3.0.1, V4.3.1.0, V4.3.2.1, V4.3.3.1, V4.3.4.1, V4.3.5.5, V4.4.0.1, V4.4.1.0, and V4.5.0.0

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