This topic describes how to synchronize data from a Db2 for LUW database to a PolarDB-X V2.0 instance by using Data Transmission Service (DTS).
- The source Db2 for LUW database and the destination PolarDB-X V2.0 instance are created. For more information about the supported data synchronization
scenarios, see Overview of data synchronization scenarios.
Note The PolarDB-X V2.0 instance must be compatible with MySQL 5.7.
- The available storage space of the destination database is larger than the total size of the data in the source database.
|Limits on the source database||
|Special cases||You must take note of the following items because the Db2 for LUW source database is a self-managed database:
Supported synchronization topologies
- One-way one-to-one synchronization
- One-way one-to-many synchronization
- One-way cascade synchronization
- One-way many-to-one synchronization
SQL operations that can be synchronized
|Operation type||SQL statement|
|DML||INSERT, UPDATE, and DELETE|
- Create database accounts and grant permissions to the accounts
Database Required permission References Db2 for LUW The DBADM permission Creating group and user IDs for a Db2 database installation and Authorities overview PolarDB-X V2.0 Read and write permissions on the destination database Manage accounts
- For more information about how to enable archive logging for Db2 for LUW databases, see Primary log archive method and Secondary log archive method.
- Go to the Data Synchronization page of the new DTS console.
- In the upper-left corner of the page, select the region where the data synchronization
- Click Create Task. On the page that appears, configure the source and destination databases.
Section Parameter Description N/A Task Name
DTS automatically generates a task name. We recommend that you specify an informative name to identify the task. You do not need to use a unique task name.
Source Database Database Type Select DB2 LUW. Access Method The instance type of the source database. In this example, Self-managed Database on ECS is selected.Note If your source database is a self-managed database, you must deploy the network environment for the database. For more information, see Preparation overview. Instance Region The region where the Db2 for LUW database resides. ECS Instance ID The ID of the Elastic Compute Service (ECS) instance on which the Db2 for LUW database is deployed. Port number The service port number of the Db2 for LUW database. Default value: 50000. Database Name The name of the source Db2 for LUW database. Database Account The database account of the destination Db2 for LUW instance. For more information about the permissions that are required for the account, see Preparations. Database Password
Enter the password of the database account.
Destination Database Database Type Select PolarDB-X 2.0. Access Method Select Cloud Instance. Instance Region The region where the destination PolarDB-X V2.0 instance resides. Instance ID The ID of the destination PolarDB-X V2.0 instance. Database Account The database account of the destination PolarDB-X V2.0 instance. For information about the permissions that are required for the account, see Preparations. Database Password
Enter the password of the database account.
- In the lower part of the page, click Test Connectivity and Proceed.
- Select objects for the task and configure advanced settings.
- Basic Settings
Parameter Description Task Stages
Incremental Data Synchronization is selected by default. You can select only Full Data Synchronization. You cannot select Schema Synchronization. After the precheck, DTS synchronizes the historical data of the selected objects from the source instance to the destination cluster. The historical data is the basis for subsequent incremental synchronization.
Processing Mode of Conflicting Tables
Precheck and Report Errors: checks whether the destination database contains tables that have the same names as tables in the source database. If the source and destination databases do not contain identical table names, the precheck is passed. Otherwise, an error is returned during precheck and the data synchronization task cannot be started.Note You can use the object name mapping feature to rename the tables that are synchronized to the destination database. You can use this feature if the source and destination databases contain identical table names and the tables in the destination database cannot be deleted or renamed. 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 consistency is not guaranteed and your business may be exposed to 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:
- During full data synchronization, DTS does not synchronize the data record to the destination database. The existing data record in the destination database is retained.
- During incremental data synchronization, DTS synchronizes 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, data may fail to be initialized. In this case, only some columns are synchronized or the data synchronization task fails.
- 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:
Select one or more objects from the Source Objects section and click the icon to move the objects to the Selected Objects section.Note You can select columns, tables, or databases as the objects to be synchronized.
Rename Databases and Tables
- To rename an object that you want to synchronize to the destination instance, right-click the object in the Selected Objects section. For more information, see Map the name of a single object.
- To rename multiple objects at a time, click Batch Edit in the upper-right corner of the Selected Objects section. For more information, see Map multiple object names at a time.
You can specify WHERE conditions to filter data. For more information, see Use SQL conditions to filter data.
Select the SQL operations to be synchronized In the Selected Objects section, right-click an object. In the dialog box that appears, select the SQL operations that you want to synchronize. For more information, see SQL operations that can be synchronized.
- Advanced Settings
Parameter Description Set AlertsSpecify whether to set alerts for the data synchronization task. If the task fails or the synchronization latency exceeds the threshold, the alert contacts will receive notifications.
- Select No if you do not want to set alerts.
- Select Yes to set alerts. In this case, you must also set the alert threshold and alert contacts.
Retry Time for Failed ConnectionSpecify the retry time for failed connections. Valid values: 10 to 1440. Unit: minutes. Default value: 120. We recommend that you set the retry time to more than 30 minutes. If DTS reconnects to the source and destination databases within the specified time, DTS resumes the data synchronization task. Otherwise, the data synchronization task fails.Note
- If multiple DTS instances have the same source or destination database, the lowest value takes effect. For example, the retry time is set to 30 minutes for Instance A and 60 minutes for Instance B, DTS retries failed connections at an interval of 30 minutes.
- When DTS retries a connection, you are charged for the DTS instance. We recommend that you specify the retry time based on your business needs. You can also release the DTS instance at your earliest opportunity after the source and destination instances are released.
- Basic Settings
- Click Next: Save Task Settings and Precheck in the lower part of the page. Note
- Before you can start the data synchronization task, DTS performs a precheck. You can start the data synchronization task only after the task passes the precheck.
- If the task fails to pass the precheck, you can click the icon next to each failed item to view details.
- You can troubleshoot the issues based on the causes and run a precheck again.
- If you do not need to troubleshoot the issues, you can ignore failed items and run a precheck again.
- Wait until the Success Rate becomes 100%. Then, click Next: Purchase Instance.
- On the Purchase Instance page, specify the Billing Method and Instance Class parameters for the data synchronization
instance. The following table describes the parameters.
Section Parameter Description Parameters Billing Method
- Subscription: You can pay for your subscription when you create an instance. We recommend that you select the subscription billing method for long-term use because it is more cost-effective than the pay-as-you-go billing method. You can save more costs with longer subscription periods.
- Pay-as-you-go: A pay-as-you-go instance is billed on an hourly basis. We recommend that you select the pay-as-you-go billing method for short-term use. If you no longer require your pay-as-you-go instance, you can release it to reduce costs.
Instance Class DTS provides several instance classes that have different performance in synchronization speed. You can select an instance class based on your business scenario. For more information, see Specifications of data synchronization instances. Subscription Length If you select the subscription billing method, set the subscription length and the number of instances that you want to create. The subscription length can be one to nine months or one to three years.Note This parameter is available only if you select the subscription billing method.
- Read and select Data Transmission Service (Pay-as-you-go) Service Terms.
- Click Buy and Start to start the data synchronization task. You can view the progress of the task in the task list.