Data Transmission Service:Migrate data from a MySQL-compatible OceanBase database to a Lindorm instance

Prerequisites

• The source OceanBase database runs OceanBase Database Community Edition V4.x.

  Note

  If the source database is an ApsaraDB for OceanBase instance, no limit is imposed on the engine edition or version of the instance. However, the binary logging feature must be enabled for the instance. For more information, see Operations related to the binlog service.

• The destination Lindorm instance is created. This instance uses the LindormTable engine and its available storage space is larger than the total size of data in the source OceanBase database. For more information, see Create an instance.

• The MySQL compatibility feature is enabled for the destination Lindorm instance. For more information, see Enable the MySQL compatibility feature.

• A namespace and a wide table are created in the destination Lindorm instance based on your business requirements to receive data. The wide table must be pre-partitioned based on full data. For more information, see Use a MySQL client to connect to and use LindormTable, Use Lindorm-cli to connect to and use LindormTable, Use Lindorm Shell to connect to LindormTable, CREATE TABLE, and Destination database: a Lindorm instance.

  Note

  We recommend that you create namespaces, tables, and columns in the Lindorm instance with the same names as the objects to be migrated in the OceanBase database.

Usage notes

Billing

SQL operations that support incremental migration

Permissions required for database accounts

For more information about how to create a database account and grant permissions to the database account, see the following topics:

• Self-managed OceanBase database: Create a tenant, Create a user, and Grant privileges.

• ApsaraDB for OceanBase instance: Create a tenant, Create a database user, and User privileges.

• Lindorm instance: Manage users.

Procedure

1. Log on to the DTS console.

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

3. In the top navigation bar, select the region in which your DTS instance resides.

4. Click Create Task to go to the task configuration page.

5. Optional. In the upper-right corner of the page, click New Configuration Page.

   Note

   • Skip this step if the Back to Previous Version button is displayed in the upper-right corner of the page.

   • Specific parameters in the new and previous versions of the configuration page may be different. We recommend that you use the new version of the configuration page.

6. Configure the source and destination databases. The following table describes the parameters.

   Section	Parameter	Description
   N/A	Task Name	The name of the task. DTS automatically generates a task name. We recommend that you specify an informative name to identify the task. You do not need to specify a unique task name.
   Source Database	Select Existing Connection	The instance that you want to use. You can choose whether to use an existing instance based on your business requirements. If you select an existing instance, DTS automatically populates the parameters for the database. If you do not use an existing instance, you must configure the database information below. Note You can register a database with DTS on the Database Connections page or the new configuration page. For more information, see Manage database connections.
   	Database Type	The type of the source database. Select ApsaraDB OceanBase for MySQL.
   	Access Method	The access method of the source database. Select a value based on the deployment location of the source database. In this example, Public IP Address is selected. Note If a self-managed database is used as the source database, you must set up the environment that is required for the self-managed database before data migration. For more information, see Preparation overview.
   	Instance Region	The region in which the source OceanBase database resides. Note If the Access Method parameter is set to Public IP Address and the region in which the OceanBase database resides is not displayed in the Instance Region drop-down list, select a region that is geographically closest to the OceanBase database.
   	Domain Name or IP	The endpoint of the source OceanBase database.
   	Port Number	The service port of the source OceanBase database. Default value: 2881.
   	IP Address in Log Proxy (Domain Name Not Supported)	The IP address of oblogproxy for the source OceanBase database.
   	Port in Log Proxy	The listening port of oblogproxy for the source OceanBase database. Default value: 2983.
   	Database Account	The account of the source OceanBase database. For more information about the permissions required for the account, see the Permissions required for database accounts section of this topic.
   	Database Password	The password that is used to access the database instance.
   Destination Database	Select Existing Connection	The instance that you want to use. You can choose whether to use an existing instance based on your business requirements. If you select an existing instance, DTS automatically populates the parameters for the database. If you do not use an existing instance, you must configure the database information below. Note You can register a database with DTS on the Database Connections page or the new configuration page. For more information, see Manage database connections.
   	Database Type	The type of the destination database. Select Lindorm.
   	Access Method	The access method of the destination database. Select Alibaba Cloud Instance.
   	Instance Region	The region in which the destination Lindorm instance resides.
   	Instance ID	The ID of the destination Lindorm instance.
   	Database Account	The database account of the destination Lindorm instance. For more information about the permissions required for the account, see the Permissions required for database accounts section of this topic.
   	Database Password	The password that is used to access the database instance.

7. In the lower part of the page, click Test Connectivity and Proceed.

   Make sure that the CIDR blocks of DTS servers are added to the whitelist of the OceanBase database. Then, click Test Connectivity.

   Important

   If the public CIDR blocks of DTS servers are added to the whitelist of the database, security risks may arise. Before you use DTS to migrate data, you must understand and acknowledge the potential risks and take preventive measures, including but not limited to the following measures: enhancing the security of your username and password, limiting the ports that are exposed, authenticating API calls, and regularly checking the whitelist and forbidding unauthorized CIDR blocks. For more information, see Add the CIDR blocks of DTS servers.

8. Configure the objects to be migrated.

   1. On the Configure Objects page, configure the objects that you want to migrate.

      Parameter	Description
      Migration Types	To perform only full data migration, select only Full Data Migration. To ensure service continuity during data migration, select Full Data Migration and Incremental Data Migration. Note If you do not select Incremental Data Migration, we recommend that you do not write data to the source database during data migration. This ensures data consistency between the source and destination databases.
      Processing Mode of Conflicting Tables	Precheck and Report Errors: checks whether the destination database contains tables that use the same names as tables in the source database. If the source and destination databases do not contain tables that have identical table names, the precheck is passed. Otherwise, an error is returned during the precheck and the data migration task cannot be started. Note If the source and destination databases contain tables with identical names and the tables in the destination database cannot be deleted or renamed, you can use the object name mapping feature to rename the tables that are migrated to the destination database. For more information, see Map object names. Ignore Errors and Proceed: skips the precheck for identical table names in the source and destination databases. Warning If you select Ignore Errors and Proceed, data inconsistency may occur and your business may be exposed to the following potential risks: If the source and destination databases have the same schema, and a data record has the same primary key as an existing data record in the destination database, the following scenarios may occur: During full data migration, DTS does not migrate the data record to the destination database. The existing data record in the destination database is retained. During incremental data migration, DTS migrates the data record to the destination database. The existing data record in the destination database is overwritten. If the source and destination databases have different schemas, only specific columns are migrated or the data migration task fails. Proceed with caution.
      Capitalization of Object Names in Destination Instance	The capitalization of database names, table names, and column names in the destination instance. By default, DTS default policy is selected. You can select other options to make sure that the capitalization of object names is consistent with that of the source or destination database. For more information, see Specify the capitalization of object names in the destination instance.
      Source Objects	Select one or more objects from the Source Objects section. Click the icon to add the objects to the Selected Objects section. Note You can select columns, tables, or databases as the objects to be migrated. If you select tables or columns as the objects to be migrated, DTS does not migrate other objects, such as views, triggers, or stored procedures, to the destination database.
      Selected Objects	To change the name of an object to be migrated in the destination instance, right-click the object in the Selected Objects section. For more information, see Map object names. To remove one or more objects that are selected for migration, click the objects in the Selected Objects section and then click the icon to move the objects to the Source Objects section. Note If you use the object name mapping feature to rename an object, other objects that are dependent on the object may fail to be migrated. To specify WHERE conditions to filter data, right-click a table in the Selected Objects section. In the dialog box that appears, specify the conditions. For more information, see Specify filter conditions. To select the SQL operations performed on a specific database or table, right-click the object in the Selected Objects section. In the dialog box that appears, select the SQL operations that you want to migrate.

   2. Click Next: Advanced Settings to configure advanced settings.

      Parameter	Description
      Dedicated Cluster for Task Scheduling	By default, DTS schedules the data migration task to the shared cluster if you do not specify a dedicated cluster. If you want to improve the stability of data migration tasks, purchase a dedicated cluster. For more information, see What is a DTS dedicated cluster.
      Retry Time for Failed Connections	The retry time range for failed connections. If the source or destination database fails to be connected after the data migration task is started, DTS immediately retries a connection within the retry time range. Valid values: 10 to 1440. Unit: minutes. Default value: 720. We recommend that you set the parameter to a value greater than 30. If DTS is reconnected to the source and destination databases within the specified retry time range, DTS resumes the data migration task. Otherwise, the data migration task fails. Note If you specify different retry time ranges for multiple data migration tasks that share the same source or destination database, the value that is specified later takes precedence. When DTS retries a connection, you are charged for the DTS instance. We recommend that you specify the retry time range based on your business requirements. You can also release the DTS instance at the earliest opportunity after the source database and destination instance are released.
      Retry Time for Other Issues	The retry time range for other issues. For example, if DDL or DML operations fail to be performed after the data migration task is started, DTS immediately retries the operations within the retry time range. Valid values: 1 to 1440. Unit: minutes. Default value: 10. We recommend that you set the parameter to a value greater than 10. If the failed operations are successfully performed within the specified retry time range, DTS resumes the data migration task. Otherwise, the data migration task fails. Important The value of the Retry Time for Other Issues parameter must be smaller than the value of the Retry Time for Failed Connections parameter.
      Enable Throttling for Full Data Migration	Specifies whether to enable throttling for full data migration. During full data migration, DTS uses the read and write resources of the source and destination databases. This may increase the loads of the database servers. You can enable throttling for full data migration based on your business requirements. To configure throttling, you must configure the Queries per second (QPS) to the source database, RPS of Full Data Migration, and Data migration speed for full migration (MB/s) parameters. This reduces the loads of the destination database server. Note You can configure this parameter only if you select Full Data Migration for the Migration Types parameter.
      Enable Throttling for Incremental Data Migration	Specifies whether to enable throttling for incremental data migration. To configure throttling, you must configure the RPS of Incremental Data Migration and Data migration speed for incremental migration (MB/s) parameters. This reduces the loads of the destination database server. Note You can configure this parameter only if you select Incremental Data Migration for the Migration Types parameter.
      Environment Tag	The environment tag that is used to identify the DTS instance. You can select an environment tag based on your business requirements. In this example, you do not need to configure this parameter.
      Configure ETL	Specifies whether to enable the extract, transform, and load (ETL) feature. For more information, see What is ETL? Valid values: Yes: configures the ETL feature. You can enter data processing statements in the code editor. For more information, see Configure ETL in a data migration or data synchronization task. No: does not configure the ETL feature.
      Monitoring and Alerting	Specifies whether to configure alerting for the data migration task. If the task fails or the migration latency exceeds the specified threshold, the alert contacts receive notifications. Valid values: No: does not configure alerting. Yes: configures alerting. In this case, you must also configure the alert threshold and alert notification settings. For more information, see the Configure monitoring and alerting when you create a DTS task section of the Configure monitoring and alerting topic.

9. Save the task settings and run a precheck.

   • To view the parameters to be specified when you call the relevant API operation to configure the DTS task, move the pointer over Next: Save Task Settings and Precheck and click Preview OpenAPI parameters.

   • If you do not need to view or have viewed the parameters, click Next: Save Task Settings and Precheck in the lower part of the page.

   Note

   • Before you can start the data migration task, DTS performs a precheck. You can start the data migration task only after the task passes the precheck.

   • If the task fails to pass the precheck, click View Details next to each failed item. After you analyze the causes based on the check results, troubleshoot the issues. Then, run a precheck again.

   • If an alert is triggered for an item during the precheck:

     • If an alert item cannot be ignored, click View Details next to the failed item and troubleshoot the issues. Then, run a precheck again.

     • If the alert item can be ignored, click Confirm Alert Details. In the View Details dialog box, click Ignore. In the message that appears, click OK. Then, click Precheck Again to run a precheck again. If you ignore the alert item, data inconsistency may occur, and your business may be exposed to potential risks.

10. Wait until Success Rate becomes 100%. Then, click Next: Purchase Instance.

11. Purchase a data migration instance.

    1. On the Purchase Instance page, configure the Instance Class parameter for the data migration instance. The following table describes the parameters.

       Section	Parameter	Description
       New Instance Class	Resource Group	The resource group to which the data migration instance belongs. Default value: default resource group. For more information, see What is Resource Management?
       	Instance Class	DTS provides instance classes that vary in the migration speed. You can select an instance class based on your business scenario. For more information, see Instance classes of data migration instances.

    2. Read and agree to Data Transmission Service (Pay-as-you-go) Service Terms by selecting the check box.

    3. Click Buy and Start. In the message that appears, click OK.

       You can view the progress of the task on the Data Migration page.