OMS V4.1.0

Version information

• Version: V4.1.0

• Previous version: V4.0.2

• Version release date: July 15, 2023

• Supported upgrade versions:

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

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

• We recommend that you use oblogproxy V2.1.0 or later.

Supported versions of data terminals

New features

Enhanced support for OceanBase Database V4.1.0

• Data migration

  • Added Reverse Increment for migrating data from heterogeneous databases such as Oracle, OceanBase, TiDB, and PostgreSQL to OceanBase Database V4.1.0. This feature is mainly used for data reflux after data migration is completed.

  • Added support for migrating data to OceanBase Database V4.1.0 from databases of earlier versions.

    Added support for migrating data between OceanBase Databases V4.1.0.

Added support for migrating data from OceanBase Database V4.1.0 to MySQL, Oracle, and DB2 LUW databases.

• Data Synchronization

• Added support for synchronizing data from OceanBase Database V4.1.0 to big data terminals such as Kafka, DataHub, and RocketMQ.

Support for more heterogeneous databases and instance types

• Incremental Synchronization: Added support for synchronizing incremental data from the Oracle compatible mode of OceanBase Database to a MySQL database. Currently, only incremental DML data synchronization involving tables with unique keys is supported.

• Message Format Compatibility: When synchronizing data from the MySQL compatible mode of OceanBase Database to Kafka, DataHub, and RocketMQ, DebeziumFlatten and DebeziumSmt JSON formats are supported. This facilitates easy integration with downstream big data ecosystems.

Enhanced usability

• Batch operations: In terms of data migration and data synchronization project management, six common batch operation control capabilities have been added, including batch project startup, batch project suspension, etc., which significantly improve the efficiency of user operations and maintenance transmission projects.

• Batch Operations: Added six common batch operation capabilities for managing data migration and synchronization projects, including the ability to batch start and pause projects. These enhancements significantly boost user efficiency in operating and maintaining transmission projects.

  • Incremental DDL: Added support for creating migration and synchronization projects using the shuttle box method, and provided incremental DDL support.

    Notice

    Objects involved in incremental DDL operations must be included in the selected synchronization objects.

• Performance Monitoring of Full Synchronization: Added real-time progress monitoring for full synchronization in data synchronization projects, including metrics such as progress, estimated total rows, synchronized rows, RPS, and traffic.

• Added new monitoring charts, including source and target RPS, source and target synchronization traffic, source average read time, source average slice time, and target average write time.

• Interaction Optimization for Migration Types: Adjusted the default migration type for migrating from a MySQL database to the MySQL compatible mode of OceanBase Database to All Tables. This change reduces the load on background resources when querying primary key tables, thus significantly shortening the time required to load migration objects and improving user experience.

• User Interface Optimization:

  • Resolved the issue of hidden project names due to excessive length.

  • Added project names to alert messages.

  • Enhanced connection details with more basic data source information.

  • Optimized the failure prompt button and failure information in structure migration projects.

  • Added Import CSV File and Download CSV Template File buttons below the imported objects list.

• Optimization for Forward Switchover: Added logic to delete related store files after stopping the source store during forward switchover, and to clear relevant information after stopping the source Incr-Sync. This resolves the issue of data unexpected synchronization caused by component misstart, thereby ensuring data security.

• Optimization for Data Source Editing: Restructured the data source editing page to allow only changes to username and password in the database section, and only changes to AK/SK in the message object section. This resolves the issue of errors when modifying unsupported attributes.

• Optimization for Precheck:

  • Added support for saving project information after a precheck failure. This meets the user requirement to temporarily save projects and resolve issues later.

  • Added support for removing tables with unsupported engine types or that do not exist in the target during precheck.

Bug fixes

Known issues