OMS V3.4.0

Version information

• Version number: V3.4.0

• Previous version: V3.3.1

• Version release date: October 21, 2022

• Version upgrade support:

  • Versions earlier than OMS V3.2.1 must be upgraded to V3.2.1 first.

  • OMS V3.2.1 or later can be directly upgraded to V3.4.0.

Compatible database versions

New features

Data migration and synchronization

• Migrating and synchronizing data tables without unique keys from a MySQL database to a MySQL tenant of OceanBase Database are supported.

• Migrating and synchronizing data from a PostgreSQL 10.x database to a MySQL tenant of OceanBase Database are supported.

• Data synchronization from a MySQL tenant of OceanBase Database to an Alibaba Cloud Kafka instance is supported.

• Monitoring the execution time of SQL statements in the full migration step is supported to help you effectively identify performance-related issues.

• Monitoring the execution time of SQL statements and the statistics of incremental data in the incremental synchronization and reverse incremental migration steps is supported to show the project performance and track changed objects.

• Adding and removing tables in the progress of a synchronization or migration project are supported to make the O&M of the product easier.

• Enterprise-level operation audit is supported to track user operations. This improves product security.

• Importing partitioned tables into an OceanBase database by partition is supported. This improves the full migration performance in an all-around manner and reduces the overall migration time.

Feature changes and optimization

Interaction experience optimization

• The verification code mechanism is provided to improve security.

• Displaying the current point in time of the synchronization components in the timestamp format is supported.

• Frequent operations on the project details page, such as view objects and view component monitoring metrics, are optimized to make your operations easier.

Feature upgrades

• You can skip the precheck and forward switchover steps.

• You can skip unsupported DDL statements with one click. This simplifies user operations and improves product usability.

• Automatically clearing virtual columns that are manually created in the forward switchover step is supported. This simplifies subsequent operations.

• The project monitoring and alerting logic is optimized to ensure that projects can be monitored in special scenarios.

• The schema migration, full migration, and full verification processes are optimized to avoid the impact of table processing failures on the running of a project.

• You can enable force character set conversion when the character set of the source is incompatible with that of the destination.

Fixed issues

• When you query a MySQL data source, the indexes cannot be correctly identified.

• The processing of a shard of multiple index tables may cause data loss.

• When partitioned tables are synchronized from a MySQL tenant of OceanBase Database V1.4.79 to a MySQL tenant of OceanBase Database V2.2.77 in a full synchronization project, the number of subpartitions in the destination is different from that in the source.

• The calling of internal APIs occasionally fails, which causes project errors that cannot be fixed.

• An internal web service has an NGINX zero-day vulnerability.

Known issues

• [Data migration] If a table has a foreign key, the "Tables doesn't exist" error message is returned during the schema migration of the table.

  Temporary solution: Click Retry and create the table again.

• [Data migration] When a project is paused, the displayed status of the data migration step is inaccurate.

  Temporary solution: If the overall performance of the project is normal, you can ignore this issue.