OMS V3.2.1

Version information

• Version number: 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 versions of data terminals

New features

Data migration and synchronization

• This version supports data migration and synchronization between or among multiple types of data sources.

  • Supports data migration or synchronization from/to the Oracle compatible mode of OceanBase Database of the DB2 LUW database type in both directions.

  • Supports data migration or synchronization between the Oracle compatible mode and the MySQL compatible mode of OceanBase Database across regions, as well as disaster recovery and data dual-active scenarios.

  • Supports data migration or synchronization from the Oracle compatible mode of OceanBase Database to an Oracle database.

  • Supports data migration or synchronization from the MySQL compatible mode of OceanBase Database to a MySQL database.

  • Supports synchronization of data from the Oracle compatible mode of OceanBase Database to a DataHub instance.

• The data migration feature now supports automatic synchronization of incremental DDL changes.

• The data migration and synchronization feature between or among databases now supports row filtering.

• Supports extracting data from standby sources such as Oracle ADG and MySQL Slave to reduce resource consumption of the primary database.

• When synchronizing data from OceanBase Database to a Kafka instance, the Kafka instance can be securely authenticated.

• When synchronizing data from OceanBase Database to a RocketMQ instance, row filtering is supported for data.

• Supports adding a DBP data source as the source for data synchronization, to synchronize logical tables. This feature supports automatic synchronization of incremental DDL changes.

• Supports data migration and synchronization between homogeneous or heterogeneous OceanBase clusters managed by different OCP instances.

Controls

• When you create a data migration project, you can configure matching rules of migration objects to select migration objects. This allows you to quickly and batch set migration objects.

• When you import migration objects, you can configure the information of migration databases and tables. This version also allows you to configure the mapping rules of migration databases and tables.

• The project tag feature is provided to help you manage data migration and data synchronization projects.

System management

• Support for configuring DingTalk alert channels.

• The overview page of the monitoring and operation module provides the regions of OMS instances and data sources, to facilitate monitoring of the operating status of the OMS system and management of data sources by region.

Feature changes and optimizations

Optimizations of features and performance

• The data synchronization performance between heterogeneous indexes at the source and target sides is improved.

• When you synchronize data from OceanBase Database to a Kafka instance, support for source large transactions is improved, and the memory resources of the synchronization write module are reduced.

• The implementation of multi-table join aggregation and merge aggregation is optimized.

• The check of incremental synchronization settings is optimized when an Oracle database serves as the source. Only table-level supplemental logging need to be enabled for an Oracle database.

• The dependency of obproxy bound in the deployment phase is deleted. obproxy is uniformly entered when each data source is added for an OceanBase database instance.

Optimization of interactive experience

• The database and table renaming controls are upgraded. The save and data filtering features are clearer and more convenient.

• The homepage of the product list is heavily revamped. The information structure and style are comprehensively upgraded.

• The overview page of the monitoring and operation module is newly designed. The regions, top 5 hosts by resources, and top 5 components by resources are provided.

Documentation optimization

• HTML product documentation is embedded in the console for real-time reference during OMS use.

• Reference descriptions are provided for new monitoring items, including possible causes and solutions of alerts.

• More detailed descriptions are provided for each parameter in the system parameters module.

Bug fixes

Data migration

• Fixed the issue where a full verification fails during data synchronization from the Oracle compatible mode of OceanBase Database to a DB2 LUW database because a Binary_Float field is set as the primary key.

• Fixed the issue where a table with a Binary field set as the primary key fails the verification during data synchronization from a DB2 LUW database to the Oracle compatible mode of OceanBase Database.

• Fixed the issue where an error of Failed to complete http request: Read timed out is returned when full migration or full verification fails during data migration from the MySQL compatible mode of OceanBase Database to a DataHub instance.

• Fixed the issue where incremental migration fails and an error of ORA-00911: invalid character is returned during data migration from an Oracle database of version 11g to the Oracle compatible mode of OceanBase Database.

• Fixed the issue where the logic of processing the WITH [CASCADED | LOCAL] CHECK OPTION clause is incorrect during view construction.

• Fixed the issue where a unknown column exception is thrown during schema migration from an Oracle database to the Oracle compatible mode of OceanBase Database.

• Fixed the issue where a date field in an Oracle database fails the full verification.

• Fixed the issue where JSON data cannot be verified during a full verification of data in a MySQL database.

Data Synchronization

• Fixed the issue where columns added to a logical table are not synchronized to the corresponding physical table during synchronization from the logical table to the physical table.

• Fixed the issue where an internal server error occurs when you view a data synchronization project after OMS 3.1.0 is upgraded to OMS 3.2.1.

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

• Fixed the issue where the topic name restriction does not conform to the specifications supported by RocketMQ.

• Fix the issue in the data synchronization project where the maximum default value of 16 for the full sync thread pool is set as a system parameter configuration.

• Fixed the issue where synchronization from a logical table is lost after a synchronization breakpoint of the logical table fails to be resumed.

• Fixed the issue where an index column attribute of NOT NULL is supported for synchronization to the MySQL compatible mode of OceanBase Database during synchronization from a logical table.

• Fixed the issue where data is lost due to failed resumption of breakpoint during synchronization from a logical table.

• Fix the issue where the Connector component does not have enough threads in the full slice thread pool during logical table synchronization.

System management

• Fixed the issue where the length of a username configured on the front end is inconsistent with that configured on the back end when a user is created.

• Fixed the issue where rules are displayed with spaces between them when you view migration objects or migration rules.

Known issues

• The log component on the frontend cannot display continuous spaces in the backend, which causes the SKIPDDL parameter of the real-time synchronization component to fail.

• After OMS 3.1.0 is upgraded to OMS 3.2.1, an INNER_ERROR message is displayed on the details page of a 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 the Oracle compatible mode of OceanBase Database, take note of the following limitations:

  • Tables with virtual columns cannot be migrated.

  • If the numeric data type of a column in the target database is wider than that in the source database, data overflow may occur during reverse incremental migration.

  • If a Range-partitioned table in the DB2 LUW database is migrated to the first partition of the Oracle compatible mode of OceanBase Database without an upper limit, data overflow may occur during reverse incremental migration.

• When you migrate data from the Oracle compatible mode of OceanBase Database to a DB2 LUW database, take note of the following limitations:

  • UK tables to which NULL values are migrated will result in data loss.

  • Tables whose names exceed the length limit are not supported. Otherwise, an error is returned because the key name is too long.

  • Operations involving non-decimal numbers are not supported. Otherwise, an error is returned during structural migration.

  • The verification of the CHAR type may be inconsistent.

  • Specifying a special function as the default value of a column is not supported. Otherwise, an error will be returned. Example: INTERVAL, ROUND

  • During full verification, data may be inconsistent for CHAR columns in tables whose field types are CHAR or NCHAR in the DB2 LUW database.

• The "Specify character encoding and length options" setting is not supported during data migration from the Oracle compatible mode of OceanBase Database to an Oracle database.

• After you clone a data migration project of OceanBase Database and remove the target database, if you select the same database as the source database, the number of displayed tables is different.

• When you migrate data from a logical table of OceanBase Database to a DataHub instance, row filtering in the ETL options fails to parse special symbols.

Get support

Access relevant documentation

You can access the latest documentation for OMS from OceanBase Migration Service Documentation.

Contact Technical Support

For any questions, contact OceanBase Technical Support.