OMS V4.2.4

Version information

• Version: V4.2.4

• Previous version: V4.2.3 BP1

• Release date: November 28, 2024

• Upgrade path:

  • OMS versions earlier than 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 the integration of underlying components and issues with supporting DataHub tasks, tasks upgraded from V3.2.1 and later will not display after the upgrade. If your upgrade involves DataHub tasks and the version is V3.2.1, contact technical support.

New features

Expanded migration scope

• Support for data migration from ApsaraDB for DRDS to OceanBase Database MySQL-compatible tenants

  To better support offline data migration from Apsara Stack ApsaraDB for DRDS to OceanBase Database, OMS V4.2.4 introduces a new feature for migrating data from ApsaraDB for DRDS to OceanBase Database MySQL-compatible tenants. This includes full data migration, incremental DML synchronization, and full data verification. This feature helps users automatically obtain the DRDS topology and create tasks for migrating data from physical RDS to OceanBase Database MySQL-compatible tenants through simple page interactions.

• Expanded supported versions for data sources

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

New feature characteristics

• Support for throttling configuration

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

• Online DDL tool compatibility

  For forward incremental synchronization from MySQL databases to OceanBase Database MySQL-compatible tenants, as well as reverse incremental synchronization from OceanBase Database MySQL-compatible tenants to MySQL databases, if Online DDL tools are used at the source, users can select corresponding compatibility options (including Alibaba Cloud DMS, gh-ost, and pt-osc) to 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 destination or source of reverse incremental migration is OceanBase Database V4.3.x or later, OMS V4.2.4 allows users to configure the table storage type (including options for default, row-based storage, columnar storage, and hybrid row-column storage) for schema migration and new table objects. The default option relies on the tenant parameter default_table_store_format for storage type settings, while other options allow users to set the table object storage format according to their preferences, meeting OLAP migration needs for OceanBase Database V4.3.x and later.

• Support for data synchronization matching rules

  The capability for configuring matching rules in data synchronization tasks from databases to message queues is now supported. This allows users to select synchronization objects with simple wildcard rule configurations when creating data synchronization tasks, reducing the cost of object selection. Supported data synchronization task types 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 resources available to each task component, achieving overall resource allocation control for OMS clusters. This addresses the issue of insufficient platform resources caused by multiple departments sharing a single OMS instance, leading to resource contention.

• Support for custom DDL synchronization types

  For data migration or synchronization tasks involving DDL synchronization, users can now customize the DDL types to be synchronized. By clicking Customize DDL/DML Configuration, users can access the configuration dialog box. This includes fine-grained control over DDL synchronization.

• Table migration for replicated tables

  For OceanBase Database versions later than V4.2.0, OMS V4.2.4 supports migrating replicated table attributes through schema migration and incremental DDL, ensuring structural consistency between the two OceanBase databases.

Feature enhancements

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

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

• When an Oracle database or an Oracle-compatible tenant of OceanBase Database serves as the source, the precheck is enhanced to check whether foreign key dependency objects are to be synchronized. This ensures data integrity of mutually dependent objects.

• When a MySQL database is migrated to a MySQL-compatible tenant of OceanBase Database, the precheck is enhanced to remind you to pay attention to the primary key that is of the INT type and indicates an auto-increment column. This prevents the values of the primary key from jumping and exceeding the boundary after the data is migrated to OceanBase Database.

• The range of resetting the timestamp of incremental synchronization is restricted. You can adjust the timestamp only to a point in time when log storage is enabled in the store. This ensures the stability of the adjusted timestamp.

• Alerts can be triggered for exceptions of the Store components of a task. This ensures that you can be promptly notified of Store exceptions and helps ensure the stability of the task.

• The incremental synchronization component provides the parameter replaceOnUpdateMode, which is used to convert the UPDATE operations at the target of synchronization from MySQL or a MySQL-compatible tenant of OceanBase Database to REPLACE operations. The parameter is disabled by default.

Ease-of-use improvements

• Optimized the schema migration and post-index interaction process. Objects with exceptions are displayed with priority.

• By default, schema migration skips the creation of objects that already exist.

• Adjusted the archiving 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.

• OceanBase Database V4.2.1 BP4 and later no longer limit the size of the migrated object list to 64 KB.

• Added a filtering feature for check results.

• Added task names to the list on the Store page under Operations and Monitoring > Components.

• Added a space matching rule detection feature.

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

Feature matrix

Data migration

Data synchronization

Supported database versions

The following tables describe the database versions supported by OceanBase Migration Service (OMS) and OceanBase Cloud Platform (OCP) for data migration and synchronization.

• For OceanBase Database of a version earlier than V4.x, the current OMS version supports pulling full and 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 OceanBase Database V4.x, the OMS versions supported for pulling incremental data from OceanBase Database as the source are listed in the following tables. Other versions are not supported and require a hot store upgrade.

  • OMS V4.2.4

    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, V4.3.3.1

  • OMS V4.2.4 BP

    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, V4.3.4.0

The following tables list the database versions and OCP versions supported for data migration and synchronization.