OMS V4.2.5

Version information

• Version: V4.2.5

• Previous version: V4.2.4 BP1

• Release date: March 24, 2025

• Upgrade path:

  • OceanBase Migration Service (OMS) of a version earlier than V3.2.1 must be first upgraded to V3.2.1.

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

    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

SSO by using SAML 2.0

Security Assertion Markup Language (SAML) 2.0 is a standard development protocol based on XML. It is widely applied for single sign-on (SSO) in federated identity authentication scenarios. By adapting to the SAML 2.0 protocol, OMS V4.2.5 supports automatic login to multiple application systems after you connect to a unified SSO platform through simple configuration. This reduces the account management costs.

Support for standalone OceanBase Database

OMS of earlier versions does not support standalone OceanBase Database. OMS V4.2.5 supports standalone OceanBase data sources. OMS directly connects to the OBServer node and starts OceanBase Change Data Capture (CDC) by using the RootServer list to implement schema migration, full migration, and incremental synchronization.

Upgraded deployment mode

In OMS of earlier versions, the management image and component image are packaged as a whole for deployment. In other words, the management image and component image are deployed on the same node. In this deployment mode, the migration tasks will be restarted upon each upgrade or configuration change, compromising the real-time performance of business. OMS V4.2.5 allows you to deploy and upgrade the management image and component image separately. You can flexibly customize an upgrade strategy as needed to ensure business stability.

Stability enhancements

• The logic for stopping the Store component is optimized. Specifically, the main process is also ended when the Store component is stopped. This way, after you configure parameters, the parameter settings take effect upon a component restart.

• The logic for integrating CDC versions is optimized. This avoids an excessively large installation package caused if too many CDC versions are integrated.

• An alert message will be sent after a component is abnormal and the high availability (HA) module is triggered. You can promptly intervene to avoid unexpected production faults.

• OMS V4.2.5 allows you to deploy cluster manager (CM) databases in multiple regions. Requests in different regions are routed to the nearby CM database. This avoids the issue of high latency resulted from cross-region access when a single CM database is deployed and shared.

Security enhancements

• OMS V4.2.5 supports key rotation. This feature can significantly reduce risks of password cracking.

Ease-of-use improvements

• The DB2 Store component can pull and parse the log file that is named connector.log and stored in the connector/ directory. You can view the logs on the GUI to facilitate troubleshooting.

• The password strategies of OMS are aligned with those of OceanBase Cloud Platform (OCP) and OceanBase Developer Center (ODC) to ensure consistency across products in the ecosystem.

Feature matrix

Data migration

Data synchronization

Supported database versions

The versions of OceanBase Database that support data migration and data synchronization are as follows:

• OceanBase Database of a version earlier than V4.x can be used as the source to pull full and incremental data or as the target to write data.

• OceanBase Database V4.x can be used as the source to pull full data or as the target to write data.

• For the incremental data synchronization of OceanBase Database V4.x, OMS V4.2.4 and V4.2.4 BP support only the following versions. For other versions, you can perform hot store version upgrade to enable the support.

  • V4.1.x

  • V4.2.1.10, V4.2.2.1, V4.2.3.0, V4.2.4.0, V4.2.5.2, V4.3.0.1, V4.3.1.0, V4.3.2.1, V4.3.3.1, V4.3.4.1, and V4.3.5.0

The following table describes the versions of other databases and OceanBase Cloud Platform (OCP) that support data migration and data synchronization.