OMS V3.3.0

Version information

• Version: V3.3.0

• Previous version: V3.2.2

• Version release date: April 3, 2022

• Supported upgrade versions:

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

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

Supported versions of data terminals

New features

Data migration and synchronization

• Supports migrating and synchronizing data from the MySQL compatible mode of OceanBase Database to the DB2 LUW database.

• When migrating data from an Oracle database to the Oracle compatible mode of OceanBase Database, supports only incremental synchronization.

• When synchronizing data from OceanBase Database to Kafka, supports schema synchronization and full synchronization.

• When synchronizing data from OceanBase Database, MySQL, DBP, or IDB as the data source to a DataHub instance of the BLOB data type, supports schema synchronization, full synchronization, and incremental synchronization.

• After you create a non-unique index, the full migration is at least 30% faster, significantly improving the full migration performance.

• Supports more Kafka versions (V1.0 and V2.X) to meet different environment requirements.

• When synchronizing data from OceanBase Database, DBP, or IDB to a DataHub instance of the BLOB data type, supports incremental DDL operations to improve completeness of the feature.

• Supports five general JSON data formats and three common data partitioning rules.

Data source management

The physical data source of OceanBase Database no longer requires mandatory association with OCP, expanding support for more business scenarios.

Feature updates and optimizations

Interaction experience optimization

• Supports the Open API for monitoring project status, facilitating integration with your own monitoring system.

• Added the component management module, improving the management structure.

• Displays commonly used operation buttons on the frontend for easy access, and added confirmation prompts to prevent accidental operations.

• Optimized DingTalk alerts, provided clear frontend instructions for forward switching, and added strong prompts for migrating table types, enhancing overall usability.

• Simplified the data synchronization project creation process, allowing you to quickly create projects.

• Implemented the deployment parameters in a wizard-like interface to reduce deployment complexity.

• Optimized the synchronization timestamp selection logic to improve system robustness.

• Supports quick access to projects from components, strengthening the association between projects and components and reducing user operation steps.

Feature upgrades

• When migrating data from an Oracle database to the Oracle compatible mode of OceanBase Database, supports more incremental DDL types, significantly enhancing core capabilities.

• Supports user management with multiple admin roles, password encryption storage, and console access control in HTTPS mode, establishing an enterprise-level security architecture.

• Supports five general JSON formats and three data partitioning rules, with added business tag options to meet diverse customer needs.

• Support the ability to roll back in case of upgrade failure, ensuring a safe and worry-free upgrade.

• Optimized response speed on monitoring pages to enhance user satisfaction.

Bug fixes

• Fixed the issue where full verification of time values between the MySQL database and OceanBase Database in the MySQL compatible mode takes a long time due to time zone settings.

• Fixed the issue where an error is returned if the binary type exceeds 32673 during schema migration from OceanBase Database in the MySQL compatible mode to DB2 LUW.

• Fixed the issue where data types are inconsistent during data verification from OceanBase Database in the MySQL compatible mode to DB2 LUW.

• Fixed the issue where an error is returned during data write for the bit type during project migration from OceanBase Database in the MySQL compatible mode to DB2 LUW.

• Fixed the issue where an error is returned during full verification of binary and varchar table structures during project migration from OceanBase Database in the MySQL compatible mode to DB2 LUW.

• Fixed the issue where an error is returned during binary256 schema migration from OceanBase Database in the MySQL compatible mode to DB2 LUW.

• Fixed the issue where execution of full correction SQL statements for the time type at the source fails during project migration from a DB2 LUW database to OceanBase Database in the Oracle compatible mode.

• Fixed the issue where reverse incremental DDL operations fail to delete multiple partitions during project migration from an Oracle database to OceanBase Database in the Oracle compatible mode.

• Fixed the issue where syntax verification for ETL time type fails during project migration from a MySQL database to OceanBase Database in the MySQL compatible mode.

• Fixed the issue where consumed data of the BLOB type in OceanBase Database in the Oracle compatible mode (GBK encoding) is displayed in garbled characters in a DataHub project.

• Fixed the issue where the date type value of 0000-00-00 synchronized from OceanBase Database in the MySQL compatible mode to a Kafka project is displayed as an empty value after full synchronization.

• Fixed the issue where the full synchronization progress always displays as 0 during project migration from OceanBase Database in the Oracle compatible mode to a DataHub project.

• Fixed the issue where consumption values of numeric and time types at the boundaries fail during full synchronization from OceanBase Database in the MySQL compatible mode to a Kafka project.

• Fixed the issue where the project frequently reports Out of Memory errors.

• Optimized the underlying incremental synchronization component to solve the issue where, during reverse incremental migration of tables without unique keys from an Oracle database to OceanBase Database in the Oracle compatible mode, data that should be synchronized to the source (the Oracle database) is not synchronized in database scenarios with large transactions.

Known issues

• The drop index incremental DDL statement does not support filtering statements without table names.

• If the incremental data migration from OceanBase Database in the MySQL compatible mode to a Kafka project results in an abnormal numeric format, the connector fails.

• After the name of a table migrated from an Oracle database to OceanBase Database in the Oracle compatible mode is changed by using incremental DDL statements, DML operation synchronization for the table fails.

• During project migration from OceanBase Database in the MySQL compatible mode to a DB2 LUW database, if a multi-partition table with a global unique index has its partition key values updated, data loss may occur during migration.

• During project migration from OceanBase Database in the MySQL compatible mode to a MySQL database, the data types of JSON columns are inconsistent, but the actual database values are consistent.

Limitations

• During project migration from OceanBase Database in the MySQL compatible mode to a DB2 LUW database, only tables with primary keys or not null unique keys are supported.

• You can only create a data synchronization project by creating a topic or selecting an existing topic.

• During full synchronization from OceanBase Database to a Kafka or DataHub (Blob) project, only tables with primary keys or not null unique keys are supported.

• For a table without a unique key that is migrated from an Oracle database to a DataHub project, you must specify a sharding column.

• In table and topic mappings between Oracle, MySQL, OceanBase, DBP, and IDB and a DataHub (Tuple) project, one table corresponds to one topic.

• During project migration from OceanBase Database in the MySQL compatible mode to a DB2 LUW database, the MySQL compatible mode of the source table is case-insensitive.