FAQ

This topic describes the frequently asked questions about updating OceanBase Migration Service (OMS) Community Edition.

What versions of OMS Community Edition can be upgraded to V3.3.1-CE?

OMS Community Edition support upgrade only from the previous version. The upgrade path is V3.2.2-CE > V3.3.0-CE > V3.3.1-CE.

Must I back up the original database before the upgrade?

We recommend that you back up the original database before you start the upgrade. The backup of the original database is a fail-safe measure in the upgrade process. Once the upgrade fails, you can start the original OMS Community Edition container.

If you do not back up the original database, make sure that the name of the new database is the same as that of the original database. In addition, you cannot roll back to the original database if the upgrade fails.

How can I control the interval for pulling data from the Store component?

You can enable high availability (HA) to automatically create a new store. The prerequisite for automatic store creation is that the number of stores under the subtopic does not exceed the value of the subtopicStoreNumberThreshold parameter of ha.config. By default, the number of stores under a subtopic is 5.

1. Log on to the OMS Community Edition console.

2. In the left-side navigation pane, choose System Management > System Parameters.

3. On the System Parameters page, find ha.config and click the edit icon in the Value column.

4. In the Modify Value dialog box, set enable to true to enable HA.

5. Set the perceiveStoreClientCheckpoint parameter to true to enable data pulling from the Store component for downstream component.

   If you set perceiveStoreClientCheckpoint to false, you need to set the refetchStoreIntervalMin parameter to the desired value. This parameter specifies the time interval, in minutes, for pulling data from the Store component.

   For example, if the tasks monitored in the original container are all executed in real time, you plans to stop the original container at 4:00 pm and the upgrade is expected to complete at 5:00 pm, we recommend that you set the refetchStoreIntervalMin parameter to 90 minutes. This interval is the sum of a 60-minute period (between the container stop time and the upgrade end time) and a 30-minute redundant period (based on the business traffic).

If I modify the parameters of some processes before the upgrade, do the parameters exist after the upgrade?

• If you modify the parameters of the JDBCWriter, Connector, or Checker component, the modified parameters still exist after the upgrade succeeds.

• If you modify the parameters of the Store component, such as a whitelist-related parameter, the subtopic configuration is updated accordingly, and the modified parameters still exist after the upgrade succeeds.

What do I do to resolve configuration compatibility issues when I upgrade OMS Community Edition V3.2.2-CE to V3.3.1-CE?

If you do not add the dbType parameter before the upgrade, the data synchronization projects cannot run. You can choose one of the following methods to fix the issue after the upgrade.

Notice:

If you use OMS Community Edition V3.3.0-CE and it contains data synchronization projects created by using OMS Community Edition V3.2.2-CE, 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 Connector component. If any of the two parameters exists, no fix is required.

Method 1: Modify the configuration

1. Log on to the OMS Community Edition console.

2. In the left-side navigation pane, choose OPS & Monitoring > Component > Connector.

3. On the Connector tab, click Update in the Actions column of the target connector.

4. In the Update Configurations dialog box, hover the pointer over the blank area on the right side of the source field and click + to add the dbType parameter.

   

   Notice:

   If the checkpoint parameter is not specified, you need to specify the corresponding information.

5. After the configuration is completed, click Update.

Method 2: Re-create the project

1. Log on to the OMS Community Edition console.

2. In the left-side navigation pane, click Data Synchronization.

3. On the Synchronization Projects page, click Clone in the Actions column of the project.

4. Configure information about the cloned project and change the synchronization start timestamp to a timestamp before the upgrade.

5. After the configuration is completed, start the data synchronization project and make sure that it runs normally.

6. Delete the previous data synchronization project.