Create a project to migrate data from a MySQL tenant of OceanBase Database to a DB2 LUW database

This topic describes how to use OceanBase Migration Service (OMS) to migrate data from a MySQL tenant of OceanBase Database to a DB2 LUW database.

Prerequisites

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

• DB2 LUW 10.1, 10.5, 11.1, and 11.5 for Linux and AIX are supported. OceanBase Database V2.2.7x, V3.1.0, and V3.2.x are supported.

• Retain logs of OceanBase Database for at least one day in case of unexpected pullback.

Limits

• OMS cannot migrate a table without the primary key from a MySQL tenant of OceanBase Database to a DB2 LUW database.

• The ARM architecture does not support reverse incremental migration from a MySQL tenant of OceanBase Database to a DB2 LUW database.

• In long-term synchronization between databases, OMS does not support triggers in the destination database.

• If the character set used by the source database is UTF-8, we recommend that you use UTF-8 or a greater character set for the destination database.

• Length limits

  • The data of the CHAR or BINARY type cannot exceed 255 bytes in length in a DB2 LUW database. If the data of the CHAR or BINARY type written to a MySQL tenant of OceanBase Database exceeds 255 bytes, OMS reports an error when the data is migrated to a DB2 LUW database.

  • The data of the VARCHAR or BINARY type cannot exceed 32,673 bytes in length in a DB2 LUW database. If the data of the VARCHAR or BINARY type written to a MySQL tenant of OceanBase Database exceeds 32,673 bytes, OMS reports an error when the data is migrated to a DB2 LUW database.

  • The Decimal(dp, ds) in a DB2 LUW database is equivalent to the NUMERIC of a MySQL tenant of OceanBase Database. The length of dp cannot exceed 31 and must be greater than that of ds.

    The number written to a MySQL tenant of OceanBase Database cannot exceed the maximum allowed number. By default, the data of the NUMERIC, INT, SMALLINT, and NUMBER(*, s) types is 38 bytes in length in a MySQL tenant of OceanBase Database. You need to explicitly define the NUMBER(p,s) to the length that is compatible with the business application and the source and destination databases.

  • The data of the NCHAR type cannot exceed 63 bytes in length in a DB2 LUW database or 2,000 bytes in a MySQL tenant of OceanBase Database. Therefore, if a field where data of the NCHAR type exceeds 63 bytes in a MySQL tenant of OceanBase Database, the field is truncated when it is migrated to a DB2 LUW database. This causes data loss.

• Data type limits

  • The data of the TIME type in a DB2 LUW database cannot be migrated as the partitioning key.

  • The data of the XML type is not supported.

  • We do not recommend that you use CODEUNITS16 or CODEUNITS32 to define or store multi-byte data of the NCHAR, GRAPHIC, or other types.

  • The default value of the BLOB-type data cannot be modified.

  • When you migrate data from OceanBase Database V1.4.x, OMS does not support primary keys that contain data of the FLOAT or DOUBLE type.

  • Spaces on the right side of data of the VARCHAR and VARGRAPHIC types are not compared in a DB2 LUW database. If the primary key lacks a space during incremental data synchronization, the data can become inconsistent. This causes data loss in the destination database.

  • Note that when a data type in a DB2 LUW database is converted to the LOB type in a MySQL tenant of OceanBase Database, the data of the LOB type cannot exceed 48 MB in size.

• Case sensitivity limits

  • If the data in the source MySQL tenant of OceanBase Database is case-sensitive, OMS of the current version does not support the migration of the data to a DB2 LUW database.

  • If the data in the source MySQL tenant of OceanBase Database is case-insensitive and the database names and table names are in lowercase, the database names and table names of the destination DB2 LUW database during schema migration or DDL migration are also in lowercase by default.

• In a project of migration from a MySQL tenant of OceanBase Database to a DB2 LUW database, when the MySQL tenant is of a version earlier than V3.2.x and has a multi-partition table with global unique indexes, if you update the value of a partitioning key of the table, data may be lost during migration.

• If you change the unique index of the destination, you must restart the incremental synchronization. Otherwise, the data may be inconsistent.

Data type mappings

Create a data migration project

1. Create a data migration link.

   1. Log on to the OMS console.

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

   3. On the Data Migration page, click Create Migration Project in the upper-right corner.

2. On the Select Source and Destination page, configure the parameters.

   Parameter	Description
   Migration Project Name	We recommend that you set it to a combination of Chinese characters, digits, and letters. It must not contain any spaces and cannot exceed 64 characters in length.
   Label	Click the field and select the target tag from the drop-down list. You can click Manage Tags to create, modify, and delete tags. For more information, see Use tags to manage data migration projects.
   Source	If you have created a data source for the MySQL tenant of OceanBase Database, select it from the drop-down list. Only tables with primary keys (tables containing the pk and not null uk fields) and tables with unique keys are displayed. If you have not created a data source, click Create Data Source in the drop-down list and create a data source in the dialog box that appears on the right. For more information, see Create OceanBase Database physical tables as a data source.
   Destination	If you have created DB2 LUW data sources, select one from the drop-down list. If you have not created a data source, click Create Data Source in the drop-down list and create a data source in the dialog box that appears on the right. For more information, see Create a DB2 LUW data source. Notice The column specified as the unique key in a DB2 LUW database must have the NOT NULL constraint.

3. Click Next.

4. In the dialog box that appears, click OK.

   Note that this project supports only tables with a primary key or a non-null unique index and other tables are automatically filtered out.

5. On the Select Migration Type page, specify related parameters.

   Options are available for Migration Type include Schema Migration, Full Migration, Incremental Synchronization, Full Verification, and Reverse Incremental Migration.

   Migration type	Limits
   Full Migration	If you select Full Migration, we recommend that you collect the statistics of the MySQL tenant of OceanBase Database before the data migration.
   Incremental Synchronization	Options for Incremental Synchronization are DML Synchronization and DDL Synchronization. The DML operations for synchronization are Insert, Delete, and Update. You can select the operations as needed. For more information, see Supported DDL operations in incremental migration from a MySQL tenant of OceanBase Database to a DB2 LUW database and limits. During the incremental synchronization from a MySQL tenant of OceanBase Database to a DB2 LUW database, the comments are automatically filtered. Incremental Synchronization has the following limits: If you do not select DDL Synchronization, ensure that the source database involves no modifications and that the incremental DML data has been synchronized to the destination before DDL modifications. Then, perform related DDL operations in the source and destination databases respectively. If you do not select DDL Synchronization, for DDL operations on tables in the migration link, perform these operations in the destination database first. Otherwise, data migration may fail. If you have selected DDL Synchronization, when you perform a DDL operation for incremental migration that is not supported by OMS in the source database, data migration may fail.
   Full Verification	If you select Full Verification, we recommend that you collect the statistics of the MySQL tenant of OceanBase Database and use the RUNSTATS statement to collect the statistics of the DB2 LUW database before the full verification. If you have selected Incremental Synchronization but did not select all DML statements in DML Synchronization, OMS does not support full data verification in this scenario.
   Reverse Incremental Migration	You cannot select Reverse Incremental Migration in the following cases: Multi-table aggregation and synchronization are enabled. Multiple schemas are configured in a rule to match one type of objects.

6. (Optional) Click Next.

   When the source database is a MySQL tenant of OceanBase Database:

   • If incremental synchronization needs to be performed, specify the ConfigUrl, username, and password.

   • If only schema migration needs to be performed, specify the username and password.

   If you select Schema Migration or Incremental Synchronization but no corresponding parameters are configured for the data source of the source MySQL tenant of OceanBase Database, the More about Data Sources dialog box appears, prompting you to configure related parameters. For more information, see Create OceanBase Database physical tables as a data source.

   After you configure the parameters, click Test Connectivity. After the test succeeds, click Save.

7. Click Next. On the Select Migration Objects page, select the migration objects and migration scope.

   You can select one of the following two modes to migrate objects: Specify Objects or Match Rules. If you select DDL Synchronization, only the Match Rules option is available.

   • Select Specify Objects. Then 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 of one or more databases as the migration objects.

     Notice

     • The name of a table to be migrated and the names of columns in the table must not contain Chinese characters.

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

     When you migrate data from a MySQL tenant of OceanBase Database to a DB2 LUW database, OMS allows you to import objects by using text files, rename object names, set row filters, view column information, and remove one or all objects to be migrated.

     Operation	Steps
     Import Objects	In the list on the right of the Specify Migration Scope section, click Import Objects in the upper-right corner. In the dialog box that appears, click OK. Notice 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/tables and set row filtering conditions. For more information, see Download and import the settings of migration objects. Click Validate. After the validation succeeds, click OK.
     Rename	In the list on the right of the Specify Migration Scope section, hover the pointer over the target object. Click Rename. Enter a new name and click OK.
     Settings	OMS allows you to set WHERE conditions to filter data by row and view column information. In the list on the right of the Specify Migration Scope section, hover the pointer over the target object. Click Settings. In the Settings dialog box, specify a standard SQL WHERE clause to filter data by row. The setting takes effect for full migration and incremental synchronization. Notice Add an escape character (`) for column names. Example: `col`. Only the data meeting the WHERE condition is synchronized to the destination data source, thereby filtering data by row. If row-based filtering with the WHERE clause is enabled, right-trim is forcibly performed on data of the CHAR or VARCHAR type, which may cause an inaccurate comparison of the VARCHAR data. Proceed with caution. Click OK. You can also view column information of the migration object in the View Columns section.
     Remove/Remove All	OMS allows you to remove one or more objects from the destination database during data mapping. Remove a single migration object In the list on the right of the Specify Migration Scope section, hover the pointer over the target object, and click Remove. The migration object is removed. Remove all migration objects In the list on the right of the Specify Migration Scope section, 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 for migration objects.

8. Click Next. On the Migration Options page, configure the parameters.

   Parameter	Description
   Concurrency for Full Migration	The value can be Smooth, Normal, or Fast. The amount of resources to be consumed by a full data migration task varies based on the migration performance. You can also modify the configurations of the checker component to customize the concurrency. Notice To enable this feature, select Full Migration on the Select Migration Type page.
   Full Verification Concurrency	The value can be Smooth, Normal, or Fast. Different quantities of resources of the source and destination databases are consumed at different concurrencies. You can also modify the configurations of the checker component to customize the concurrency.
   Incremental Record Retention Time	The duration that incremental parsed files are cached in OMS. A longer retention period indicates more disk space occupied by the store component of OMS.
   Whether to Allow Destination Table to Be Not Empty During Full Migration	If destination tables are allowed to be not empty during full migration, full verification is performed in IN mode. Notice To enable this feature, select Full Migration on the Select Migration Type page.
   Whether to Allow Post-indexing	You can specify whether to allow post-indexing after full migration is completed. Post-indexing can shorten the time of full migration. Notice To enable this feature, select both Schema Migration and Full Migration on the Select Migration Type page. Only non-unique key indexes can be created after the migration is completed.

9. Click Precheck to start a precheck on the data migration project.

   During the precheck****, OMS checks the read and write privileges of the database users and the network connections of the databases. The data migration project can be started only after it passes all check items. If an error is returned:

   • You can troubleshoot the error and run the precheck again.

   • You can also click Skip in the Actions column of the precheck item that returns the error. Then, a dialog box appears, indicating the impact that may be caused if you choose to skip this check item. If you want to continue, click OK in the dialog box.

10. Click Start Project. If you do not need to start the project now, click Save to go to the details page of the data migration project. You can start the project later as needed.

OMS allows you to modify migration objects when a data migration project is running. For more information, see View and modify migration objects. After a data migration project is started, the migration objects will be executed based on the selected migration type. For more information, see the "View migration details" section in the View details of a data migration project.