OMS V3.2.2

V3.2.2

Version information

• Version number: V3.2.2

• Previous version: V3.2.1

• Version release date: December 31, 2021

• Supported upgrade versions:

  • OMS V3.2.1 can be directly upgraded to V3.2.2.

  • Other versions must be upgraded to V3.2.1 first, and then to V3.2.2.

Supported versions of data terminals

New features

• Data migration and synchronization from a DB2 LUW database of V10.1 to the Oracle compatible mode of OceanBase Database are supported.

• Data migration and synchronization from an Oracle database of V10.2 to the Oracle compatible mode of OceanBase Database are supported.

• Data migration and synchronization from an Oracle database to the MySQL compatible mode of OceanBase Database are supported.

• OceanBase data sources managed based on IDB (similar to Mycat) are added. This enables data synchronization to the MySQL compatible mode of OceanBase Database and to a DataHub instance.

Feature updates and optimizations

• The user experience is optimized as follows:

  • The input of associated information of OCP Meta Database is reduced to simplify the system.

  • The input logic of OceanBase data sources and the display logic of data source information are optimized to improve the system usability.

  • The 3-digit grouping method is used to display very large numbers for better readability.

  • The recheck feature of full verification is changed to a restore button, and prompts are added for better user understanding.

• The following features are upgraded:

  • System-level parameters are added to optimize the performance of full migration.

  • The naming rules of Kafka topics are modified to support more types of characters.

  • Illegal characters and time delivery are adapted to improve the system compatibility.

Bug fixes

• The issue where the source index names are discarded during schema migration when migrating data from a MySQL database to OceanBase Database in the MySQL compatible mode is fixed.

• The issue where data migration fails between OceanBase databases due to the presence of invalid time data in the format of "0000-00-00 00:00:00" is fixed.

• The issue where business queries become slow when Oracle flashback queries are used in an Oracle-to-Oracle compatible mode migration project in OceanBase Database is fixed.

• The issue where the monitoring data of reverse incremental traffic is inaccurate in a migration project from OceanBase Database in the Oracle compatible mode to a DB2 LUW database is fixed.

• The issue where the calculated estimated end time is incorrect during full verification is fixed.

• The issue where tables containing virtual columns cannot be migrated from a DB2 LUW database to an OceanBase database in the Oracle compatible mode is fixed.

• The issue where the verification results of CHAR or NCHAR data types are inconsistent in a data migration project from an OceanBase database in the Oracle compatible mode to a DB2 LUW database is fixed.

• The issue where the precision is not displayed when datetime(6) data is migrated to a DataHub instance from a MySQL database is fixed.

• The issue where an error is reported when a project with the same name is created after a project is deleted is fixed.

• The issue where a port is occupied when the incremental parsing component is started is fixed.

Known issues

The JDBCWriter component cannot be successfully updated when it is running in the data write-in process.

Solution : You can pause the JDBCWriter component and then update its parameters.

Limitations

• If the source data type is RAW(10), schema migration will fail in a data migration project from an Oracle database to OceanBase Database in the MySQL compatible mode.

• In a data migration project from a DB2 LUW database to OceanBase Database in the Oracle compatible mode, the DEFAULT value is not supported for the DATE data type.

• ETL is not supported in a data migration project from a DB2 LUW database to OceanBase Database in the Oracle compatible mode.

• In a data migration project from a MySQL database to OceanBase Database in the MySQL compatible mode, data verification will be inconsistent if the source and target collations are different.

• In a data migration project from a DB2 LUW database to OceanBase Database in the Oracle compatible mode, data migration will fail if the data of the VARCHAR type in the source DB2 LUW database is an empty string and the attribute is set to NOT NULL.

V3.2.2-BP1

OMS 3.2.2-BP1 focuses on upgrading the underlying components and fixing some frontend input logic issues.

Bug fixes

• Fixed the issue where the JDBCWriter component does not support the Skip_DDL parameter for DDL statements containing line break symbols.

• Fixed the issue where, in a data migration project between MySQL-compatible tenants of OceanBase Database, the JDBCWriter component fails after type conversion when ETL is configured.

• Fixed the issue where columns are added or dropped in the source data of a data migration project without enabling incremental DDL.

• Fixed the issue with the logic for selecting unique indexes in Oracle stores.

• Fixed the issue where an indexed table fails to rename in a data migration project from the MySQL compatible mode of OceanBase Database to a MySQL database.

• Fixed the issue where ETL configuration fails if the Oracle database contains only secondary partitioned tables.

• Fixed the issue where the Kafka server in a data migration project from the MySQL compatible mode of OceanBase Database contains the '-' symbol.

• Fixed the issue where Oracle Store exits unexpectedly due to an IO error: socket read timed out.

• Fixed the issue where associated OCP operations fail.

• Fixed the issue where the IDB data source returns the cluster name field as clusterName.

V3.2.2-BP2

OMS 3.2.2-BP2 addresses the Log4j security vulnerability.

Get support

Access related documentation

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

Contact Technical Support

For any questions, contact OceanBase Technical Support.