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

• Version upgrade support:

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

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

Compatible database versions

New features

• Allows you to migrate and synchronize data from a DB2 LUW V10.1 database to an Oracle tenant of OceanBase Database.

• Allows you to migrate and synchronize data from an Oracle V10.2 database to an Oracle tenant of OceanBase Database.

• Allows you to migrate and synchronize data from an Oracle database to a MySQL tenant of OceanBase Database.

• Supports IDB (similar to Mycat)-managed OceanBase data sources, so that you can synchronize data from logical tables to MySQL tenants of OceanBase Database and to DataHub instances. For more information, see the following topics:

Feature changes and optimization

• Interaction experience optimization

  • The OCP option becomes optional when you add a data source, thereby reducing the system complexity.

  • The input logic of OceanBase data sources and the display logic of data source information are optimized, thereby improving the ease-of-use of the system.

  • Long numbers are displayed with thousands separators, thereby improving readability.

  • A Restore button is provided in place of the Recheck button for the full verification feature, to help you understand the purpose of the button.

• Feature upgrades

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

  • The naming rules for Kafka topics are modified to support more character types.

  • OMS is adapted to invalid characters and time formats, to improve system compatibility.

Fixed issues

• The index names of the source database are discarded during schema migration from a MySQL database to a MySQL tenant of OceanBase Database.

• Data migration between OceanBase databases fails due to time data of invalid formats such as 0000-00-00 00:00:00.

• Business queries are slow because Oracle Store uses flashback query during data migration from an Oracle database to an Oracle tenant of OceanBase Database.

• The traffic monitoring data is inaccurate during reverse incremental migration between Oracle tenants of OceanBase Database.

• The estimated completion time is calculated incorrectly during full verification.

• Tables with virtual columns cannot be migrated during data migration from a DB2 LUW database to an Oracle tenant of OceanBase Database.

• In a project for migrating data from an Oracle tenant of OceanBase Database to a DB2 LUW database, the data of the CHAR or NCHAR type in the DB2 LUW database is inconsistent during verification.

• In a project for migrating data from a MySQL database to a DataHub instance, the precision is not displayed after data of the datetime(6) type is written to the DataHub instance.

• An error is reported when the name of a newly created project is the same as that of a deleted project.

• An error indicating that the port is occupied is reported when the incremental parsing component is started.

Known issues

Parameters cannot be updated when the incremental write component JDBCWriter is running.

Solution : Pause the JDBCWriter and update the parameters.

Limits

• When you migrate data from an Oracle database to a MySQL tenant of OceanBase Database, if the type in the source database is RAW(10), the schema migration will fail.

• When you migrate data from a DB2 LUW database to an Oracle tenant of OceanBase Database, default values are not supported for data of the Date type during schema migration.

• When you migrate data from a DB2 LUW database to an Oracle tenant of OceanBase Database, you cannot set the ETL option.

• When you migrate data from a MySQL database to a MySQL tenant of OceanBase Database, the data may be inconsistent during verification if the collations of the source and destination databases are inconsistent.

• When you migrate data from a DB2 LUW database to an Oracle tenant of OceanBase Database, if data of the VARCHAR type is an empty string and the attribute is Not Null in the DB2 LUW database, the data migration will fail.

V3.2.2-BP1

OMS V3.2.2-BP1 updatesthe underlying components of OMS, and corrects some front-end input logic.

Fixed issues

• The Skip_DDL parameter of the JDBCWriter does not support line break characters in DDL statements.

• After the ETL option is configured in a project for migrating data between MySQL tenants of OceanBase Database, type conversion results in exceptions on the JDBCWriter.

• Columns cannot be added or dropped in the source database if increment DDL statement migration is not enabled for data migration projects.

• The logic for Oracle Store to select a unique index is incorrect.

• In a project for migrating data from a MySQL tenant of OceanBase Database to a MySQL database, after a table with indexes is renamed, indexes fail to be created in the renamed table.

• The ETL option fails to be configured in an Oracle database that contains only subpartitioned tables.

• In a project for migrating data from a MySQL tenant of OceanBase Database to a Kafka instance, the Kafka instance contains hyphens (-).

• Oracle Store exits abnormally due to "IO Error: Socket read timed out".

• Association with OCP fails. The cluster name field for the IDB data sourcewas incorrect. (The cluster name field has been corrected to clusterName.)

V3.2.2-BP2

OMS V3.2.2-BP2fixes Log4j security vulnerabilities.