ApsaraDB for OceanBase:Migrate incremental data from an Oracle tenant of OceanBase Database to a MySQL database

Prerequisites

• The data transmission service has the privilege to access cloud resources. For more information, see Grant privileges to roles for data transmission.

• You have created dedicated database users for data migration in the source Oracle tenant of OceanBase Database and the destination MySQL database, and granted required privileges to the users. For more information, see Create a database user.

Limitations

• The data transmission service supports MySQL 5.5, 5.6, 5.7, and 8.0.

• The data transmission service does not support the migration of tables without primary keys from an Oracle tenant of OceanBase Database to a MySQL database.

• The data transmission service does not support triggers in the destination database. If triggers exist in the destination database, the data migration may fail.

• The data transmission service supports the migration of an object only when the following conditions are met: the database name, table name, and column name of the object are ASCII-encoded without special characters. The special characters are line breaks, spaces, and the following characters: . | " ' ` ( ) = ; / & \.

Considerations

• If the UTF-8 character set is used in the source database, we recommend that you use a compatible character set, such as UTF-8 or UTF-16, in the destination database to avoid garbled characters.

• If the clocks between nodes or between the client and the server are out of synchronization, the latency may be inaccurate during incremental synchronization or reverse incremental migration.

  For example, if the clock is earlier than the standard time, the latency can be negative. If the clock is later than the standard time, the latency can be positive.

• If you modify a unique index at the destination, you must restart the data migration task to avoid data inconsistency.

• A difference between the source and destination table schemas may result in data consistency. Some known scenarios are described as follows:

  • When you manually create a table schema in the destination, if the data type of any column is not supported by the data transmission service, implicit data type conversion may occur in the destination, which causes inconsistent column types between the source and destination databases.

  • If the length of a column at the destination is shorter than that in the source database, the data of this column may be automatically truncated, which causes data inconsistency between the source and destination databases.

• If you selected only Incremental Synchronization when you created the data migration task, the data transmission service requires that the local incremental logs of the source database be retained for at least 48 hours.

• If the source or destination database contains table objects that differ only in letter cases, the data migration results may not be as expected due to case insensitivity in the source or destination database.

Supported source and destination instance types

In the following table, OB_Oracle stands for an Oracle tenant of OceanBase Database. The source must be an OceanBase cluster instance.

Procedure

1. Log on to the ApsaraDB for OceanBase console and purchase a data migration task.

   For more information, see Purchase a data migration task.

2. Choose Data Transmission > Data Migration. On the page that appears, click Configuration for the data migration task.

   

   If you want to reference the configurations of an existing task, click Reference Configuration. For more information, see Reference the configuration of a data migration task.

3. On the Select Source and Destination page, configure the related parameters.

   Parameter	Description
   Migration Task Name	We recommend that you set it to a combination of digits and letters. It must not contain any spaces and cannot exceed 64 characters in length.
   Tag (Optional)	Select a target tag from the drop-down list. You can also click Manage Tags to create, modify, and delete tags. For more information, see Use tags to manage data migration tasks.
   Source	If you have created an Oracle tenant in OceanBase Database as a data source, select it from the drop-down list. Otherwise, click New Data Source in the drop-down list and create one in the dialog box that appears on the right. For more information about the parameters, see Create an OceanBase data source. Important For an Oracle tenant of OceanBase Database, Instance Type must be set to OceanBase Cluster Instance.
   Destination	If you have created a MySQL data source, select it from the drop-down list. Otherwise, click New Data Source in the drop-down list and create one in the dialog box that appears on the right. For more information about the parameters, see Create a MySQL data source.

4. Click Next. On the Select Migration Type page, specify migration types for the current data migration task.

   At present, only DML Synchronization is supported for Incremental Synchronization. You can select operations as needed. For more information, see Configure DDL/DML synchronization.

   

5. Click Next. On the Select Migration Objects page, select the migration objects of the current data migration task.

   You can select Specify Objects or Match Rules to specify the migration objects.

   Important

   • The names of tables to be migrated, as well as the names of columns in the tables, must not contain Chinese characters.

   • If a database or table name contains double dollar signs ($$), you cannot create the migration task.

   • If you select Specify Objects, select the objects to be migrated on the left and click > to add them to the list on the right. You can select tables and views in one or more databases as migration objects.

     The data transmission service allows you to import objects from text files, rename destination objects, set row filters, view column information, and remove a single or all migration objects.

     Note

     When you select Match Rules to specify migration objects, object renaming is implemented based on the syntax of the specified matching rules. In the operation area, you can only set filter conditions. For more information, see Configure matching rules.

     

     Operation	Description
     Import objects	In the list on the right, click Import Objects in the upper-right corner. In the dialog box that appears, click OK. Important This operation will overwrite previous selections. Proceed with caution. In the Import Objects dialog box, import the objects to be migrated. You can import CSV files to rename databases or tables and set row filtering conditions. For more information, see Download and import the settings of migration objects. Click Validate. After you import the migration objects, check their validity. Column field mapping is not supported at present. After the validation succeeds, click OK.
     Rename objects	The data transmission service allows you to rename migration objects. For more information, see Rename a database table.
     Configure settings	The data transmission service allows you to filter rows by using WHERE conditions. For more information, see Use SQL conditions to filter data. You can also view column information of the migration objects in the View Columns section.
     Remove one or all objects	The data transmission service allows you to remove a single object or all migration objects that are added to the right-side list during data mapping. Remove a single migration object In the list on the right, move the pointer over the object that you want to remove, and click Remove to remove the migration object. Remove all migration objects In the list on the right, click Remove All in the upper-right corner. In the dialog box that appears, click OK to remove all migration objects.

   • Select Match Rules. For more information, see Configure matching rules.

6. Click Next. On the Migration Options page, configure the parameters for incremental synchronization.

   

   Parameter	Description
   Write Concurrency Configuration	The concurrency for writing data to the destination during incremental synchronization. The maximum value is 512. A high write concurrency may incur excessive stress on the destination, affecting the business.
   Incremental Synchronization Rate Limit	You can choose whether to limit the incremental synchronization rate as needed. If you choose to limit the incremental synchronization rate, you must specify the records per second (RPS) and bytes per second (BPS). The RPS specifies the maximum number of data rows synchronized to the destination per second during incremental synchronization, and the BPS specifies the maximum amount of data in bytes synchronized to the destination per second during incremental synchronization. Note The RPS and BPS values specified here are only for throttling. The actual incremental synchronization performance is subject to factors such as the settings of the source and destination and the instance specifications.
   Incremental Synchronization Start Timestamp	Specify a point in time after which data is to be synchronized. The default value is the current system time. For more information, see Set an incremental synchronization timestamp.

7. Click Precheck to start a precheck on the data migration task.

   During the precheck, the data transmission service checks the read and write privileges of the database users and the network connections of the databases. A data migration task can be started only after it passes all check items. If an error is returned during the precheck, you can perform the following operations:

   • Identify and troubleshoot the problem and then perform the precheck again.

   • Click Skip in the Actions column of the failed precheck item. In the dialog box that prompts the consequences of the operation, click OK.

8. After the precheck succeeds, click Start Task.

   If you do not need to start the task now, click Save. You can start the task later on the Migration Tasks page or by performing batch operations. For more information about batch operations, see Perform batch operations on data migration tasks.

   The data transmission service allows you to modify the migration objects when a migration task is running. For more information, see View and modify migration objects and their filter conditions. After the data migration task is started, it is executed based on the selected migration types. For more information, see View migration details.

References

• Create an OceanBase data source

• Create a MySQL data source

• Configure matching rules

• View details of a data migration task