OMS V4.2.4

Version information

• Version: V4.2.4

• Previous version: V4.2.3 BP1

• Version release date: November 28, 2024

• Supported upgrade versions:

  • Versions earlier than OMS V3.2.1 require an upgrade to V3.2.1 first.

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

    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

Expanded task scope

• Support for data migration from DRDS to OceanBase Database's MySQL compatible mode

  To better support migrating data from Alibaba Cloud VPC DRDS to OceanBase Database, OMS V4.2.4 introduces a data migration feature specifically for transferring data from DRDS to OceanBase Database's MySQL compatible mode. This feature supports full migration, incremental DML synchronization, and full data verification. It simplifies the process by allowing users to automatically obtain DRDS topologies and batch create physical RDS to OceanBase Database MySQL compatible mode tasks through simple page interactions.

• Expanded versions supported for data sources

  OMS V4.2.4 now supports TiDB Database V6.x, V7.x, PostgreSQL Database V11.x, V13.x, MariaDB V10.6.x, and Kafka V3.x as sources or targets for migration and synchronization tasks.

New feature characteristics

• Support for throttling and traffic control configuration

  Data migration or synchronization tasks now support throttling and traffic control configurations. By adjusting relevant settings, users can control the traffic for full migration/synchronization, incremental synchronization, and reverse incremental synchronization. This allows for flexible adjustment of task pressure based on actual business workload, ensuring stability for the source, target, and the task itself.

• Adaptation for online DDL tools

  For forward incremental synchronization from MySQL Database to OceanBase Database's MySQL compatible mode, as well as reverse incremental synchronization from OceanBase Database's MySQL compatible mode to MySQL Database, if online DDL tools are used in the source, users can select corresponding adaptation options (including Alibaba Cloud DMS, gh-ost, and pt-osc) on the page. This helps filter out temporary tables created by the tool, ensuring task continuity and reducing data transmission costs.

• Support for columnar storage in OceanBase Database V4.3.x

  When the target or source of reverse incremental migration is OceanBase Database V4.3.x or later, OMS V4.2.4 allows configuration of the table structure storage type (including options for default, row-based storage, columnar storage, and hybrid row-column storage). It also supports configuring the storage type for new table objects in incremental DDL scenarios. The default option specifies to inherit the tenant parameter default_table_store_format. Other options indicate to set the storage format of table objects according to your configuration, meeting your needs for OLAP migration in OceanBase Database V4.3.x and later.

• Support for configuring matching rules in data synchronization tasks

  The data synchronization feature now supports matching rules, allowing users to select synchronization objects by configuring simple wildcard rules when creating a data synchronization task. This reduces the cost of selecting synchronization objects. Supported data synchronization scenarios include OceanBase -> Kafka, OceanBase -> RocketMQ, OceanBase -> Datahub, MySQL -> Datahub, and Oracle -> Datahub.

• Support for limiting user resource usage

  OMS V4.2.4 introduces a feature to limit user resource usage. Administrators can adjust the maximum number of tasks a user can create and the amount of memory a single task component can use to manage the overall resource allocation of the OMS cluster. This addresses the issue of insufficient resources on a shared OMS platform due to competition among departments.

• Support for customizing DDL synchronization type

  For data migration or synchronization tasks involving DDL synchronization, users can now define the specific types of DDL statements to synchronize. By clicking Customize DDL/DML Configuration, users can open the configuration dialog box. On the basis of existing DML configuration options, new DDL configuration options are added, enabling fine-grained control over DDL synchronization.

• Copy table migration

  For OceanBase Database V4.2.0 and later, OMS V4.2.4 supports migrating the replicated table attribute during schema migration and incremental DDL operations. This ensures structural consistency between two OceanBase databases.

Feature enhancements

• When you migrate data from a TiDB database to the MySQL compatible mode database of OceanBase Database, you can set SQL filter conditions to meet the specific data migration scenarios.

• The precheck is enhanced to check the existence of triggers on the target or reverse incremental synchronization source database to avoid the data quality risk caused by triggers.

• When the source database is an Oracle database or a MySQL database that uses OceanBase Database in the Oracle compatible mode, the precheck is enhanced to check whether the foreign key dependency objects to be synchronized are complete. This ensures the data integrity of mutually dependent objects.

• When you migrate data from a MySQL database to the MySQL compatible mode database of OceanBase Database and the primary key of the data to be migrated is an INT auto-increment column, a prompt is given to remind you of the risk that the data may overflow after it is migrated to OceanBase Database.

• The range of the reset timestamp is limited in incremental synchronization. Only timestamps that are stored in the log store are allowed. This ensures the stability of the adjusted timestamp.

• Alerts can be triggered when an exception occurs in the Store component of a task.

• The incremental synchronization component provides the replaceOnUpdateMode parameter to convert UPDATE operations in MySQL or MySQL compatible mode OceanBase Database to REPLACE operations. The parameter is disabled by default.

Ease-of-use improvements

• Optimized the structural migration and post-index interaction. Specifically, objects with exceptions are prioritized in display.

• By default, structural migration skips the creation of existing objects.

• Adjusted the archive check for OceanBase Database V4.x from a failure item to an alert item.

• The precheck for adding tables is now limited to the new table objects only.

• Removed the limit on the size of the migrated object list in OceanBase Database V4.2.1 BP4 and later.

• Added a filtering feature for check results.

• Added task name display on the Store list page under Monitoring and Maintenance > Component.

• Added a blank space matching rule detection feature.

• When synchronizing data from OceanBase Database to a DataHub instance, the restriction on the one-to-one correspondence between tables and topics is removed by default.

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.

  • OMS V4.2.4 supports the following versions:

    V4.1.x, V4.2.1.9, V4.2.2.1, V4.2.3.0, V4.2.4.0, V4.2.5.0, V4.3.0.1, V4.3.1.0, V4.3.2.1, and V4.3.3.1

  • OMS V4.2.4 BP supports the following versions:

    V4.1.x, V4.2.1.9, V4.2.1.10, V4.2.2.1, V4.2.3.0, V4.2.4.0, V4.2.5.1, V4.3.0.1, V4.3.1.0, V4.3.2.1, V4.3.3.1, and V4.3.4.0

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