How do I skip DDL statements?

Background

You can skip DDL statements that cause errors in an incremental synchronization project by updating the component configuration. The procedure is as follows:

1. Locate the DDL statement that reports an error in the error.log file.

2. Click the msg/ddl _msg.logtab and copy the DDL statement that follows the colon after the receive ddl keyword.

3. Add or update the corresponding parameters.

   Note

   • lf you use OceanBase Migration Service (OMS) V3.2.2-BP or a later version earlier than V3.3.1, you need to add or update the JDBCWriter.coordinatorFile.skipDdl parameter in the root section.

   • lf you use OMS V3.3.1 and later, you need to add or update the skipDdl parameter in the coordinator section.

OMS V3.2.2-BP or a later version earlier than V3.3.1

1. Find the DDL statement received by the source data source.

   1. Log on to the OMS console.

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

   3. On the Data Migration page, click the name of the target data migration project to go to its details page.

   4. Click View Component Monitoring in the upper-right corner.

   5. In the View Component Monitoring dialog box, click View Logs in the Actions column of the component.

   6. Click the msg/ddl_msg.log tab and copy the DDL statement that follows the colon after the receive ddl keyword. This is the statement received by the source data source.

      

2. Update the configurations of the JDBCWriter component.

   1. Go to the View Component Monitoring dialog box.

   2. Click Update in the Actions column of the JDBCWriter component.

   3. In the Update Configuration dialog box, move the pointer over the blank area next to the root parameter and click the plus sign.

   4. Enter JDBCWriter.coordinatorFile.skipDdl for Key Name and click the check sign.

   5. In the Update Configuration dialog box, find the new key name. The default value is NULL.

   6. Move the pointer over the new parameter, click the edit icon that appears, and change the value of the parameter to the DDL statement that you copied in the foregoing step. The target DDL statement follows the colon after the receive ddl keyword.

      OMS supports parameter values that contain line breaks and compares the value of JDBCWriter.coordinatorFile.skipDdl with the received DDL statements after removing spaces, line breaks, tabs, and semicolons in the statements.

      For example, assume that the received DDL statement is as follows:

      CREATE TABLE my_table (
      id INT,
      name VARCHAR(50)
      );
      

      Set the JDBCWriter.coordinatorFile.skipDdl parameter to "CREATE TABLE my_table(id INT,name VARCHAR(50))".

      To skip multiple DDL statements, separate them with ampersands (&), for example: "CREATE TABLE my_table(id INT,name VARCHAR(50))&create table test(id int not null)".

   7. Modify the value in the field and then click the OK icon.

   8. In the Update Configuration dialog box, click Update.

OMS V3.3.1 and later

1. Find the DDL statement received by the source data source.

   1. Log on to the OMS console.

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

   3. On the Data Migration page, click the name of the target data migration project to go to its details page.

   4. Click View Component Monitoring in the upper-right corner.

   5. In theView Component Monitoring dialog box, click View Logs in the Actions column of the Incr-Sync component.

   6. Click the msg/ddl_msg.log tab and copy the DDL statement that follows the colon after the receive ddl keyword. This is the statement received by the source data source.

      

2. Update the configuration of the Incr-Sync component.

   Notice

   In OMS V4.0.1 and later, the JDBCWriter component is renamed to Incr-Sync. Operations of the component remain unchanged. The Incr-Sync component is taken as an example.

   1. Go to the View Component Monitoring dialog box.

   2. Click Update in the Actions column of the Incr-Sync component.

   3. In the Update Configuration dialog box, move the pointer over the blank area next to the coordinator parameter and click the plus sign.

   4. Enter skipDdl for Key Name and click the check sign.

   5. In the Update Configuration dialog box, find the new key name. The default value is NULL.

   6. Move the pointer over the new parameter, click the edit icon that appears, and change the value of the parameter to the DDL statement that you copied in the foregoing step. The target DDL statement follows the colon after the receive ddl keyword.

      OMS supports keyword comparison. The received DDL statements that contain the specified keyword are filtered. In addition, you must specify the DDL statement that you want to skip in JSON format.

      For example, assume that the received DDL statement is as follows:

      CREATE TABLE my_table (
      id INT,
      name VARCHAR(50)
      );
      

      Set the skipDdl parameter to ["CREATE TABLE my_table"].

      To skip multiple DDL statements, specify the DDL statements in JSON format and separate them with commas (,), such as ["CREATE TABLE my_table","create table test"].

      Notice

      • You must use escape characters to escape double quotation marks (") in DDL statements. Otherwise, a JSON parsing error will be reported.
        For example, if you want to skip the create table "student" xxx statement, set the skipDdl parameter to ["create table \"student\" xxx"].

      • The value of the `skipDdl` parameter is case-sensitive.

   7. Modify the value in the field and then click the OK icon.

   8. In the Update Configuration dialog box, click OK.