Overview|V4.3.1|OceanBase Migration Service| docs|Distributed Database

Overview

Last Updated：2025-10-09 03:34:24 Updated

This topic describes the considerations, process, and limitations for upgrading OceanBase Migration Service (OMS) to V4.3.1.

Background information

OMS V3.2.1 and later support upgrade rollback. We recommend that you use a backup tool to back up the existing database, such as db_oms, to an SQL file, such as db_oms_bak.sql, before starting an upgrade. The new OMS image will run on the original db_oms database, and the database backup file, such as db_oms_bak.sql, can be used for a rollback.

Note

If you do not have a handy backup tool, contact OMS Technical Support for the documentation related to backup operations. In general, you can use mysqldump to export backup files.

The following table shows status changes of components and tasks when high availability (HA) is enabled or disabled.

Task/Component status before an upgrade	After an upgrade (HA disabled)	After an upgrade (HA enabled)
The task runs normally. The Incr-Sync component runs normally. The Store component runs normally.	The task status remains unchanged. The Incr-Sync component is abnormal. The Store component is abnormal.	The task status remains unchanged. The Incr-Sync component automatically starts. The Store component is automatically created based on the configurations. For more information, see Modify HA configurations.
The task fails. The Incr-Sync component is abnormal. The Store component is abnormal.
The task is stopped. The Incr-Sync component is stopped. The Store component runs normally.	The task status remains unchanged. The Incr-Sync component is stopped. The Store component is abnormal.	The task status remains unchanged. The Incr-Sync component is stopped. The Store component is automatically created based on the configurations. For more information, see Modify HA configurations.

Limitations

OMS V3.2.1 and later can be directly upgraded to V4.3.1. OMS of a version earlier than V3.2.1 must be first upgraded to V3.2.1.
If an oblogproxy task exists in the current version, upgrade is not supported. You must directly deploy OMS V4.3.1 and create a data migration or synchronization task.
Before you start the upgrade, make sure that data is synchronized in quasi-real-time between the source and target in data migration or synchronization tasks created by using the earlier version of OMS, and that the forward switchover process of the tasks is completed. We recommend that you do not use the new version of OMS to perform the forward switchover process.
Before you upgrade OMS V3.2.1 or V3.2.2, if DDL synchronization is involved, you must add the dbType parameter for the Incr-Sync component. If you do not add the dbType parameter before the upgrade, the synchronization tasks cannot run. You must fix the issue after the upgrade. For more information, see What do I do to resolve configuration compatibility issues when I upgrade OMS V3.2.1 or V3.2.2 to V4.3.1?.

Notice

If you are using OMS V3.3.0 and it contains data synchronization tasks created in OMS V3.2.1 or V3.2.2, the preceding issue may occur. You can fix it by using the same methods.

You can check whether the dbType or db_type parameter exists in the source configuration file of the Incr-Sync component. If either parameter exists, no fix is required.

Enterprise Edition

Community Edition