Migrate data from an AnalyticDB for MySQL database to a MySQL tenant of OceanBase Database

Background

• For the basic information about AnalyticDB for MySQL, see Basic data types.

• For information about table creation, partitioned tables, and distributed tables in AnalyticDB for MySQL, see CREATE TABLE.

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 a dedicated account for data migration from the AnalyticDB for MySQL database. For more information, see ADB data source.

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

Limitations

• Limitations on the source database

  Do not perform DDL operations that modify database or table schemas during full migration. Otherwise, the data migration task may be interrupted.

• The data transmission service supports AnalyticDB for MySQL V3.0.

• The data transmission service does not support triggers in the target database. If triggers exist in the target 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: . | " ' ` ( ) = ; / & \.

• The data transmission service does not support full verification. After the full migration is completed, verify the correctness of data to avoid data loss during the migration.

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 target database to avoid garbled characters.

• Check whether the migration precision of the data transmission service for columns of data types such as DECIMAL, FLOAT, and DOUBLE is as expected. If the precision of the target field type is lower than that of the source field type, the value with a higher precision may be truncated. This may result in data inconsistency between the source and target fields.

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

• If the source or target 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 target database.

Data type mappings

Supported source and target instance types

In the following table, OB_MySQL stands for the MySQL tenant of OceanBase Database.

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 Target page, configure the parameters.

   Parameter	Description

   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.
   Source	If you have created an ADB 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, see Create an ADB data source.
   Target	If you have created a data source for the MySQL tenant of OceanBase Database, 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.
   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.

4. Click Next. On the Select Migration Type page, select Full Data Migration.

   After a full migration task is started, the data transmission service migrates existing data from tables in the source database to corresponding tables in the target database. Only full migration is supported.

   

5. Click Next. On the Select Migration Objects page, specify migration objects for the data migration task.

   You can select Specify Objects or Match Rules to specify the migration objects. This topic describes how to specify the migration objects by using Specify Objects. For information about matching rules, see Configure and modify matching rules.

   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.

   

   1. In the Select Migration Objects section, select Specify Objects.

   2. In the Source Object(s) list of the Specify Migration Scope section, select the objects to migrate. You can select tables and views of one or more databases.

   3. Click > to add them to the Target Object(s) list.

   The data transmission service allows you to import objects from text files, rename target 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 and modify matching rules.

   Operation	Description

   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 or all synchronization 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.

6. Click Next. On the Migration Options page, configure the parameters for full migration.

   

   Parameter	Description

   Parameter	Description
   Read Concurrency	The concurrency for reading data from the source during full migration. The maximum value is 512. A high concurrency may incur excessive stress on the source, affecting the business.
   Write Concurrency	The concurrency for writing data to the target during full migration. The maximum value is 512. A high write concurrency may incur excessive stress on the target, affecting the business.
   Full Migration Rate Limit	You can choose whether to limit the full migration rate as needed. If you choose to limit the full migration rate, you must specify the records per second (RPS) and bytes per second (BPS). The RPS specifies the maximum number of data rows migrated to the target per second during full migration, and the BPS specifies the maximum amount of data in bytes migrated to the target per second during full migration. Note The RPS and BPS values specified here are only for throttling. The actual full migration performance is subject to factors such as the settings of the source and target and the instance specifications.
   Handle Non-empty Tables in Target Database	Valid values are Ignore and Stop Migration. If you select Ignore, when the data to be inserted conflicts with existing data of a target table, the data transmission service logs the conflicting data while retaining the existing data. Important If you select Ignore, data is pulled in IN mode during full verification. In this case, verification is inapplicable if the target contains data that does not exist in the source, and the verification performance is downgraded. If you select Stop Migration and a target table contains records, an error prompting migration unsupported is reported during full migration. In this case, you must process the data in the target table before continuing with the migration. Important If you click Restore in the dialog box prompting the error, the data transmission service ignores this error and continues to migrate data. Proceed with caution.

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 synchronization 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 is passed, 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 and their row filtering conditions 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 ADB data source

• Create an OceanBase data source

• Configure and modify matching rules

• View details of a data migration task