OMS V2.1.2

Version information

• Version: V2.1.2

• Previous version: V2.1.1

• Version release date: March 28, 2021

Supported versions of data terminals

New features

Data synchronization

• Added support for synchronizing data from OceanBase Database and Oracle to a DataHub instance: supports initialization of table schemas, full data synchronization, and incremental data synchronization.

• New support for OceanBase database sharding and table partitioning based on DBP to aggregate and synchronize to OceanBase database: supports logical table structure initialization, full data synchronization, and incremental data synchronization.

• Added support for synchronizing tables without primary keys from OceanBase Database in the MySQL compatible mode to a Kafka instance.

O&M monitoring

• Added component monitoring dashboards for synchronization projects, allowing you to view component status and key metrics, and update component parameters.

• Added log viewing for the Store and Connector components in a GUI, supporting search, copy, and download.

Data source management

Data sources are a prerequisite for migration tasks. Before you start data migration, you must add the source and target databases as data sources. OMS 2.1.2 allows you to add a DataHub instance as a data source.

Alert feature

• Alerts are automatically connected to the alert channel of the associated OCP cluster after deployment.

• You can mark an alert level for each synchronization project.

• You can define alert monitoring item thresholds and alert frequencies for different alert levels.

• The running status of a synchronization project is optimized and extended, and you can view the status in alerts.

Bug fixes

• Fixed an issue where schemas are not filtered when you synchronize multiple tables from the Oracle compatible mode of OceanBase Database to a Kafka instance.

• Fixed an issue where no limit is placed on the length of the topic when you synchronize data from the MySQL compatible mode of OceanBase Database to a DataHub instance.

  If the topic name is too long, the full synchronization will fail.

• Fixed an issue where the timestamp specified for creating a synchronization project from the MySQL compatible mode of OceanBase Database to a Kafka instance is not validated.

  If an invalid timestamp is specified when you create a data synchronization project, the log pulling of incremental data will fail after the project is started.

• Fixed an issue where full synchronization of bit-type data fails when you synchronize logical tables in the MySQL compatible mode of OceanBase Database to physical tables in the same compatible mode.

• Fixed an issue where tables without primary keys but with NOT NULL unique keys cannot be synchronized to a DataHub instance in full synchronization mode when data is synchronized from the MySQL compatible mode of OceanBase Database.

Known issues

When you synchronize data from OceanBase Database to a Kafka instance, the ShareplexJsonSerializer format is not supported in the LogProxy environment.

Limitations

• Take note of the following limitations when you perform real-time data synchronization from an Oracle database to a DataHub instance:

  • A primary key must be set for a table without a primary key in an Oracle database before you synchronize the table to a DataHub instance. Otherwise, the table will not be synchronized.

  • OMS does not parse the actual value of a generated column in an Oracle database. When data is synchronized to a DataHub instance, the value of the generated column is NULL.

  • If the CLOB, BLOB, RAW, or LONG RAW data type is used in an Oracle database, an INSERT operation involving these data types will trigger an INSERT or UPDATE message to be sent to a DataHub instance.

  • When data transmission is resumed for a broken link, some data (transmitted within the last minute) may be duplicated. Therefore, data deduplication is required in downstream applications.

• Take note of the following limitations when you perform real-time data synchronization from a OceanBase Database in the MySQL compatible mode to a DataHub instance:

  • Full synchronization of data from a table without a primary key in OceanBase Database in the OB_MySQL compatible mode is not supported.

  • When data transmission is resumed for a broken link, some data (transmitted within the last minute) may be duplicated. Therefore, data deduplication is required in downstream applications.

  • DataHub limits the size of a message based on the cloud environment, usually to 1 MB.

    DataHub sends messages in batches, with each batch sized no more than 4 MB. If a single message meets the conditions for sending, you can modify the Connector Sink parameter batch.size. By default, 20 messages are sent at a time within one second.

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.