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 need to be upgraded 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 DataHub tasks 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 data migration from ApsaraDB for DRDS to OceanBase Database MySQL-compatible tenant

  To better support offline data migration from Apsara Stack DRDS to OceanBase Database, OMS V4.2.4 introduces a new data migration task type for migrating data from ApsaraDB for DRDS to a MySQL-compatible tenant of OceanBase Database. This includes full migration, incremental DML synchronization, and full verification. It helps users automatically obtain the topology of ApsaraDB for DRDS and create tasks for migrating data from physical RDS to a MySQL-compatible tenant of OceanBase Database 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, and 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 task pressure adjustment based on actual business load, ensuring stability for the source, destination, and the task itself.

• Online DDL tool compatibility

  For forward incremental synchronization from a MySQL database to a MySQL-compatible tenant of OceanBase Database, as well as reverse incremental synchronization from a MySQL-compatible tenant of OceanBase Database to a MySQL database, if Online DDL tools are used at the source, users can select corresponding compatibility options (including Alibaba Cloud DMS, gh-ost, and pt-osc) on the page. This allows for filtering 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 configuration of the table structure storage type (including Default, RowStore, ColumnStore, and Hybrid options). It also supports configuring the table object storage type for new table objects in incremental DDL. The Default option indicates no additional storage type settings by OMS, relying instead on the tenant parameter default_table_store_format. 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 configuring matching rules in data synchronization

  The capability to configure matching rules is now supported for data synchronization tasks from databases to message queues. This allows users to select synchronization objects with simple wildcard rule configurations when creating a data synchronization task, 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 control the overall resource allocation of an OMS cluster by adjusting the maximum number of tasks a user can create and the amount of memory available to each task component. This is suitable for scenarios where multiple departments share a single OMS instance, leading to resource contention and insufficient platform resources.

• Support for customizing DDL synchronization type

  For data migration or synchronization tasks involving DDL synchronization, users can now customize the types of DDL statements to synchronize. By clicking Customize DDL/DML Configuration, users can access a configuration dialog box that extends the original DML configuration options with new DDL configuration options, allowing for fine-grained control over DDL synchronization.

• Support for replicating table migration

  For OceanBase Database versions later than V4.2.0, OMS V4.2.4 supports migrating the replica table attributes during schema migration and incremental DDL migration, ensuring schema 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 defined as the INT auto-increment type. This ensures that values of the primary key do not overflow after data is migrated to OceanBase Database.

• The range of reset timestamp is restricted for incremental synchronization to allow you to set only a point in time when logs are stored by the store. This ensures the stability of the reset timestamp.

• Alerts can be triggered for exceptions of the Store component 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 enabled by default to convert the UPDATE operations at the target of MySQL and OceanBase Database MySQL-compatible tenants to REPLACE operations.

Ease-of-use optimizations

• Optimized the schema migration and post-index interaction process. In the object list, exceptions are prioritized.

• By default, schema 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 now only examines new table objects, excluding the current object.

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

• Added a filtering feature for check results.

• Added task name display on the Store list page under Monitoring and Operation.

• 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 Database for data migration and synchronization.

• For OceanBase Database earlier than V4.x, the current OMS version supports pulling full data 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 incremental data synchronization to OceanBase Database V4.x, OMS V4.2.4 and V4.2.4 BP support only the following versions. For other versions, you must perform hot store version upgrade to get supported.

  • OMS V4.2.4 supported 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, V4.3.3.1

  • OMS V4.2.4 BP supported 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, V4.3.4.0

The following tables list the database versions supported by other databases and OceanBase Cloud Platform for data migration and synchronization.