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

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

Prerequisites

• You have created a corresponding schema in the destination Oracle tenant of OceanBase Database.

  You must create a corresponding schema in the destination database before migration. OMS will migrate the tables and views to the schema.

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

• You have enabled archivelog for the DB2 LUW database.

  You can perform the following steps to enable archivelog:

  1. Connect to OceanBase Database.

     db2 connect to ${db_name}
     

  2. Modify the directory of archived logs.

     db2 update db cfg for ${db_name} using LOGARCHMETH1 logpath(${your_logpath})
     

  3. Back up the logs.

     db2 backup database ${db_name} to dbbackuppath(${your_logpath})
     

  4. Stop the database.

     db2stop
     

  5. Start the database.

     db2start
     

  6. Connect to OceanBase Database.

     db2 connect to ${db_name}
     

  7. Manually archive logs.

     db2 archive log for db ${db_name}
     

  8. View archived logs.

     db2 get db cfg|grep LOG
     

• You have enabled Data Changes for the table in the store of the DB2 LUW database.

  You can execute the following statement to enable Data Changes:

  alter table ${table_name} data capture changes
  

• You have enabled log_ddl_stmt for the DB2 LUW database.

  You can execute the following statement to enable log_ddl_stmt:

  db2 update db cfg using LOG_DDL_STMTS YES
  

Limits

• DB2 LUW 10.5, 11.1, and 11.5 for Linux and AIX are supported. You can also migrate data from DB2 LUW 10.1 to an Oracle tenant of OceanBase Database V2.2.76 or a later version.

• The ARM architecture does not support the migration of data from a DB2 LUW database to an Oracle tenant of OceanBase Database.

• The DB2 LUW database can only parse an object whose name consists of letters, underscores(_), and digits, begins with a letter or underscore, and does not contain a DB2 LUW keyword.

• When you migrate data from a DB2 LUW database to an Oracle tenant of OceanBase Database, tables without a UNIQUE constraint cannot be migrated. Only tables with a UNIQUE constraint in the DB2 LUW database can be migrated during full migration and incremental synchronization.

• 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.

• When data of the LOB type in the DB2 LUW database is updated, a large number of row migrations for logs are generated compared with common scenarios. If an unknown combination of row migrations causes an unexpected exit of the store, retain the logs for OceanBase Technical Support.

• Do not use the UPDATE operation to change the primary key. Otherwise, data inconsistency may occur during row migration.

• The DB2 LUW database is mainly used to pull uncompressed logs for testing. The stability of pulling compressed logs has not been verified. Therefore, pull compressed logs with caution.

• Retain logs of the DB2 LUW database and OceanBase Database for at least three days in case of unexpected pullback.

• A column with a UNIQUE constraint cannot be null. Otherwise, data inconsistency may occur. Multiple null values are allowed in the same column with a UNIQUE constraint in OceanBase Database: null!=null. However, a column with a UNIQUE constraint in the DB2 LUW database cannot be null. A unique index allows null values, but null=null.

  For example, the unique (c1, c2) (null, null) index of OceanBase Database can be inserted multiple times, while a UNIQUE constraint of the DB2 LUW database does not allow null values. If a unique index is used, (null, null) can be inserted only once.

  Therefore, incompatibility occurs due to null values when OceanBase Database uses unique indexes. Do not use unique keys that allow null columns. Otherwise, errors can occur during schema migration. During incremental synchronization, a NOT NULL constraint is added to the corresponding column, and an error occurs when a null value is written to the column.

  In addition, if you create a unique index in OceanBase Database during a DDL operation for incremental migration, make sure that all columns with unique indexes are not null. Otherwise, the DB2 LUW database returns an error.

• The user parsed by the DB2 LUW database must have the sysadm privilege on the corresponding schema. Otherwise, the user cannot obtain logs.

• If a NOT NULL constraint is added to the schema of the destination Oracle tenant of OceanBase Database, null strings generated by the source DB2 LUW database cannot be written to the destination.

• In a project of reverse incremental migration from a DB2 LUW database to an Oracle tenant of OceanBase Database, when the Oracle 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 the rename operation is performed during incremental migration and the source or destination table is not in the synchronization list, the rename operation is ignored. After the rename operation is completed, restart full verification. The full verification will fail because the renamed table is not synchronized to the destination database.

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

Data type mappings

Conversion rules for schema migration

Notice

• The CHAR and VARCHAR2 data types in an Oracle tenant of OceanBase Database can store multi-byte encoded data. Therefore, if single-byte encoding units are used in a reverse conversion, the data types may not be long enough.

• In a DB2 LUW database, the lengths of data types as well as the OCTETS, CODEUNITS16, and CODEUNITS32 encoding units must be considered for data storage.
  Only DB2 LUW 10.5 and later support the OCTETS and CODEUNITS32 encoding units.

• Data of the CLOB and BLOB types must be less than 48 MB in size.

• Data of the LONG, ROWID, BFILE, LONG RAW, XMLType, and UDT types cannot be migrated.

• The problem of full data inconsistency exists in tables with the FLOAT, DOUBLE, or REAL type as the primary key.

Limits

• The maximum timestamp precision of a DB2 LUW database is 12, while that of an Oracle tenant of OceanBase Database is 9. Therefore, the data is truncated when it is migrated from a DB2 LUW database to an Oracle tenant of OceanBase Database. The data that will be truncated cannot be used as the primary key or unique key.

• Length limits

  • The data of the CHAR or BINARY type cannot exceed 255 bytes in length in a DB2 LUW database. If the data written to an Oracle tenant of OceanBase Database exceeds 255 bytes in length, an error will occur during reverse synchronization.

  • The data of the VARCHAR or BINARY type cannot exceed 32,673 bytes in length in a DB2 LUW database. If the data written to an Oracle tenant of OceanBase Database exceeds 32,673 bytes in length, an error will occur during migration.

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

    The number written to an Oracle tenant of OceanBase Database cannot exceed the maximum allowed number. By default, the data of the NUMBER, INT, SMALLINT, and NUMBER(*, s) types is 38 bytes in length in an Oracle 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.

• Data type limits

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

  • 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.

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 DB2 LUW data sources, select one from the drop-down list. Only tables with primary keys or 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 a DB2 LUW data source. Notice The column specified as the unique key in a DB2 LUW database must have the NOT NULL constraint.
   Destination	If you have created Oracle tenants in OceanBase Database as 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 OceanBase Database physical tables as a data source.

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 use the RUNSTATS statement to collect the statistics of the DB2 LUW database before 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 Dynamic DDL operations during data migration between an Oracle tenant of OceanBase Database and a DB2 LUW database. Incremental Synchronization has the following limits: If OMS uses the ARM architecture, Incremental Synchronization is not supported. 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 DB2 LUW database and the Oracle tenant of OceanBase Database before 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. If you select Reverse Incremental Migration but the ConfigUrl, username, or password is not configured for the data source of the destination Oracle 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 Synchronization DDL, 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 DB2 LUW database to an Oracle tenant of OceanBase Database, OMS allows you to import objects through text, 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.