OMS V3.2.1

Version information

• Version: V3.2.1

• Previous version: V3.1.0

• Version release date: November 10, 2021

• Supported upgrade versions: OMS V2.1.0, V2.1.2, V2.2.0, and V3.1.0 can be directly upgraded to V3.2.1.

Supported data terminals

New features

Data migration and synchronization

• Support for multiple data sources and combinations of data migration and synchronization from source to target endpoints has been added.

  • Support for migrating or synchronizing data between DB2 LUW databases and OceanBase Database in Oracle compatible mode in both directions.

  • Support for migrating or synchronizing data between OceanBase Database instances in Oracle compatible mode and those in MySQL compatible mode, including cross-region disaster recovery and data dual-live scenarios.

  • Support for migrating or synchronizing data from OceanBase Database in Oracle compatible mode to an Oracle database.

  • Support for migrating or synchronizing data from OceanBase Database in MySQL compatible mode to a MySQL database.

  • Support for synchronizing data from OceanBase Database in Oracle compatible mode to DataHub.

• Incremental DDL automatic synchronization has been added to data migration.

• Row filtering has been added to database-to-database data migration and synchronization.

• Support for extracting data from standby databases such as Oracle ADG and MySQL Slave to reduce resource consumption on the primary database has been added.

• Support for securely authenticating to a Kafka instance has been added when synchronizing data from OceanBase Database to Kafka.

• Support for configuring row filtering for data being synchronized to RocketMQ has been added.

• Support for adding a DBP data source as a data synchronization source to synchronize logical tables has been added. This feature also supports incremental DDL automatic synchronization.

• Support for migrating and synchronizing data between OceanBase clusters managed by different OCP instances within a single OMS instance has been added.

Management

• When creating a data migration project, you can configure matching rules for migration objects to select migration objects, which allows you to quickly and batch set migration objects.

• When importing migration objects, in addition to supporting text-based configuration of migration databases and tables, you can also configure mapping rules for migration databases and tables.

• Project tags have been added to help you manage data migration and synchronization projects.

System management

• Support for configuring DingTalk alert channels has been added.

• The overview page of the monitoring and maintenance module now displays the regions of OMS nodes and data sources, allowing you to monitor the OMS system status by region and manage data sources.

Feature changes and optimizations

Feature and performance optimizations

• Improved data synchronization performance when indexes are heterogeneous between the source and target endpoints.

• Enhanced support for large transactions at the source endpoint when synchronizing data from OceanBase Database to Kafka, reducing memory resource consumption in the synchronization write module.

• Optimized the implementation of multi-table join aggregation and merge aggregation scenarios.

• Optimized incremental synchronization configuration checks for Oracle databases. Now, only table-level supplemental logging needs to be enabled on the source Oracle database.

• Removed the obproxy dependency from the deployment stage. The obproxy for OceanBase Database instances is now entered when each data source is added.

User experience optimizations

• The rename controls for databases and tables have been upgraded. The save and data filtering entries are now clearer and more convenient.

• The product list page has been completely redesigned, with an upgraded information structure and style.

• The overview page of the monitoring and maintenance module has been redesigned. It now displays region attributes and allows sorting by top 5 host resources and component resource usage within a region.

Documentation optimizations

• Product HTML documentation is now embedded in the console for easy reference while using OMS.

• Reference information for alert monitoring items has been added, including possible causes of alerts and solutions.

• Detailed descriptions of system parameters have been provided.

Fixed issues

Data migration

• Fixed the issue where the full verification of the data synchronization project from OceanBase Database in Oracle compatible mode to a DB2 LUW database failed due to the Binary_float field being used as the primary key.

• Fixed the issue where the verification of the data synchronization project from a DB2 LUW database to OceanBase Database in Oracle compatible mode failed due to the Binary field being used as the primary key.

• Fixed the issue where the full migration and full verification page of the data migration project between OceanBase Database in MySQL compatible mode failed and reported the error Failed to complete http request: Read timed out.

• Fixed the issue where the incremental migration of the data migration project from Oracle Database 11G to OceanBase Database in Oracle compatible mode failed and reported the error ORA-00911: invalid character.

• Fixed the issue where the logic for handling WITH [CASCADED | LOCAL] CHECK OPTION clause in view construction SQL was incorrect.

• Fixed the issue where the structure migration of the data migration project from Oracle Database to OceanBase Database in Oracle compatible mode failed and reported the error unknown column.

• Fixed the issue where the full verification of the data synchronization project failed due to the illegal Date type in Oracle Database.

• Fixed the issue where the full verification of the data synchronization project failed due to the unsupported JSON type in MySQL Database.

Data synchronization

• Fixed the issue where the columns added to a logical table were not synchronized to the physical table.

• Fixed the issue where the internal server error was reported when viewing a data synchronization project after upgrading OMS from 3.1.0 to 3.2.1.

• Fixed the issue where the synchronization type was displayed incorrectly on the details page of the data synchronization project from OceanBase Database in MySQL compatible mode to DataHub.

• Fixed the issue where the naming restrictions of Topics did not match those supported by RocketMQ.

• Fixed the issue where the maximum default value of the full slice thread pool for full synchronization was incorrectly set as a system parameter.

• Fixed the issue where data was lost due to the synchronization breakpoint failure.

• Fixed the issue where the index column attributes could not be all set to Not Null when synchronizing a logical table to OceanBase Database in MySQL compatible mode.

• Fixed the issue where data was lost due to the failed resumption of synchronization after a breakpoint.

• Fixed the issue where the Connector component had insufficient full slice thread pool resources during logical table synchronization.

System management

• Fixed the issue where the username length was inconsistent between the frontend and backend configurations when creating a user.

• Fixed the issue where each rule was separated by a space when viewing migration objects and migration rules.

Known issues

• The frontend log component cannot display continuous spaces, causing the SKIPDDL parameter of the real-time synchronization component to be ineffective.

• After upgrading OMS from 3.1.0 to 3.2.1, the INNER_ERROR information is displayed on the details page of the data migration project.

Limitations

• Oracle Store does not support tables with column names longer than 30 characters: Schema or table or column name exceeding 30 bytes not supported.

• When you migrate data from a DB2 LUW database to an OceanBase database in Oracle compatible mode, the following limitations apply:

  • Tables with virtual columns cannot be migrated.

  • If the numeric type of the destination database is greater than that of the source database, data overflow may occur during reverse incremental migration.

  • If the range partition table of the DB2 LUW database is migrated to the OceanBase database in Oracle compatible mode, and the first partition has no upper limit, data overflow may occur during reverse incremental migration.

• When you migrate data from an OceanBase database in Oracle compatible mode to a DB2 LUW database, the following limitations apply:

  • Tables with unique keys (UKs) that allow NULL values cannot be migrated. This may result in data loss.

  • Tables with excessively long names cannot be migrated. This may result in errors due to excessively long primary key names.

  • Tables with non-decimal numbers cannot be migrated. This may result in errors during schema migration.

  • During full verification, the verification of CHAR types may be inconsistent.

  • Tables with column default values that use special functions cannot be migrated. This may result in errors. For example, INTERVAL and ROUND.

  • In the DB2 LUW database, if the field type of a table is CHAR or NCHAR, the full verification data may be inconsistent.

• When you migrate data from an OceanBase database in Oracle compatible mode to an Oracle database, you cannot configure the "Define character encoding and length options" option.

• When you clone a bidirectional data migration project from an OceanBase database, if you remove the destination database and select the same source database again, the number of displayed tables may be inconsistent.

• When you migrate data from a logical table in an OceanBase database to DataHub, the row filtering option in ETL may fail to correctly parse special symbols.