Synchronize data from Db2 for LUW to AnalyticDB for PostgreSQL

Prerequisites

• You have created a destination AnalyticDB for PostgreSQL instance. For more information, see Create an instance.

• If you want to perform full synchronization, the storage space of the destination database must be greater than the space occupied by the source database.

Considerations

Billing

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

For more information about the synchronization topologies and related considerations, see Synchronization topologies.

Supported SQL operations

Preparations

• Create accounts and grant permissions

  Database	Required permissions	Authorization method
  Db2 for LUW	DBADM permissions	Create a user
  AnalyticDB for PostgreSQL	Read and write permissions on the destination database that contains the objects to be synchronized	Create and manage a database account Note You can also use an account that has the RDS_SUPERUSER permissions. For more information, see Manage users and permissions.

• Enable the log archiving feature for the Db2 for LUW database. For more information, see logarchmeth1 - Primary log archive method configuration parameter and logarchmeth2 - Secondary log archive method configuration parameter.

Procedure

1. Go to the Data Synchronization Tasks page.

   1. Log on to the DMS console.

   2. In the top navigation bar, click Data + AI.

   3. In the left-side navigation pane, choose DTS (DTS) > Data Synchronization.

   Note

   • Operations may vary based on the mode and layout of the DMS console. For more information, see Simple mode console and Customize the layout and style of the DMS console.

   • You can also go to the Data Synchronization Tasks page of the new DTS console.

2. Click Create Task to open the task configuration page.

3. Configure the source and destination databases.

   Section	Parameter	Description
   N/A	Task Name	DTS automatically generates a task name. We recommend that you specify a descriptive name for easy identification. The name does not need to be unique.
   Source Database	Select Existing Connection	Select the registered database instance with DTS from the drop-down list. The database information below is automatically configured. Note In the DMS console, this configuration item is Select a DMS database instance. If you have not registered the database instance or do not need to use a registered instance, manually configure the database information below.
   	Database Type	Select DB2 for LUW.
   	Connection Type	Select a connection type based on the deployment location of the source database. In this example, we use a Self-managed Database on ECS. Note If the source instance is a self-managed database, you must also complete the required preparations.
   	Instance Region	Select the region where the Db2 for LUW database resides.
   	Replicate Data Across Alibaba Cloud Accounts	For this example, select No, as the database instance belongs to the current Alibaba Cloud account.
   	ECS Instance ID	Enter the ID of the ECS instance where the Db2 for LUW database is deployed.
   	Port Number	Enter the service port of the Db2 for LUW database. The default port is 50000.
   	Database Name	Enter the name of the source Db2 for LUW database that contains the objects to be synchronized.
   	Database Account	Enter the database account of the Db2 for LUW database. For information about permission requirements, see Create accounts and grant permissions.
   	Database Password	Enter the password for the specified database account.
   Destination Database	Select Existing Connection	Select the registered database instance with DTS from the drop-down list. The database information below is automatically configured. Note In the DMS console, this configuration item is Select a DMS database instance. If you have not registered the database instance or do not need to use a registered instance, manually configure the database information below.
   	Database Type	Select AnalyticDB for PostgreSQL.
   	Connection Type	Select Alibaba Cloud Instance.
   	Instance Region	Select the region where the destination AnalyticDB for PostgreSQL instance resides.
   	Instance ID	Select the ID of the destination AnalyticDB for PostgreSQL instance.
   	Database Name	Enter the name of the destination database in the AnalyticDB for PostgreSQL instance.
   	Database Account	Enter the database account of the destination AnalyticDB for PostgreSQL instance. For information about permission requirements, see Create accounts and grant permissions.
   	Database Password	Enter the password for the specified database account.

4. After the configuration is complete, click Test Connectivity and Proceed at the bottom of the page. In the CIDR Blocks of DTS Servers dialog box, click Test Connectivity.

   Note

   Ensure that the IP address blocks of the DTS service are added to the security settings of the source and destination databases, either automatically or manually, to allow access from DTS servers. For more information, see Add the IP address whitelist of DTS servers.

5. Configure the task objects.

   1. On the Configure Objects page, specify the objects to synchronize.

      Parameter	Description
      Synchronization Types	The synchronization types. By default, Incremental Data Synchronization is selected. You must also select Schema Synchronization and Full Data Synchronization. After the precheck is complete, DTS synchronizes the historical data of the selected objects from the source database to the destination cluster. The historical data is the basis for subsequent incremental synchronization.
      DDL and DML Operations to Be Synchronized	Select the DDL or DML operations to be synchronized at the instance level. For information about supported operations, see Supported SQL operations. Note To select SQL operations for a database or table, right-click a synchronization object in the Selected Objects box and select the SQL operations from the dialog box that appears.
      Processing Mode of Conflicting Tables	Precheck and Report Errors: Checks for tables with the same names in the destination database. If any tables with the same names are found, an error is reported during the precheck and the data synchronization task does not start. Otherwise, the precheck is successful. Note If you cannot delete or rename the table with the same name in the destination database, you can map it to a different name in the destination. For more information, see Database Table Column Name Mapping. Ignore Errors and Proceed: Skips the check for tables with the same name in the destination database. Warning Selecting Ignore Errors and Proceed may cause data inconsistency and put your business at risk. For example: If the table schemas are consistent and a record in the destination database has the same primary key or unique key value as a record in the source database: During full data synchronization, DTS retains the destination record and skips the source record. During incremental synchronization, DTS overwrites the destination record with the source record. If the table schemas are inconsistent, data initialization may fail. This can result in only partial data synchronization or a complete synchronization failure. Use with caution.
      Storage Engine Type	Select the storage engine type for the destination tables. The default value is Beam. Note This parameter is available only when the kernel version of the destination AnalyticDB for PostgreSQL instance is v7.0.6.6 or later, and Synchronization Types is selected for Schema Synchronization.
      Capitalization of Object Names in Destination Instance	Configure the case-sensitivity policy for database, table, and column names in the destination instance. By default, the DTS default policy is selected. You can also choose to use the default policy of the source or destination database. For more information, see Case policy for destination object names.
      Source Objects	In the Source Objects box, click the objects, and then click to move them to the Selected Objects box. Note Synchronization is supported at the table level. Other objects such as views, triggers, and stored procedures are not synchronized to the destination database.
      Selected Objects	To rename a single object in the destination instance, right-click the object in the Selected Objects box. For more information, see Map a single object name. To rename multiple objects in bulk, click Batch Edit in the upper-right corner of the Selected Objects box. For more information, see Map multiple object names in bulk. Note To select SQL operations at the database or table level, right-click an object in the Selected Objects list, and then select the desired SQL operations in the dialog box that appears. To set a WHERE clause to filter data, right-click a table in the Selected Objects list, and then specify the filter condition in the dialog box that appears. For more information, see Set filter conditions.

   2. Click Next: Advanced Settings.

      Parameter	Description
      Dedicated Cluster for Task Scheduling	By default, DTS uses a shared cluster for tasks, so you do not need to make a selection. For greater task stability, you can purchase a dedicated cluster to run the DTS synchronization task. For more information, see What is a DTS dedicated cluster?.
      Retry Time for Failed Connections	If the connection to the source or destination database fails after the synchronization task starts, DTS reports an error and immediately begins to retry the connection. The default retry duration is 720 minutes. You can customize the retry time to a value from 10 to 1,440 minutes. We recommend a duration of 30 minutes or more. If the connection is restored within this period, the task resumes automatically. Otherwise, the task fails. Note If multiple DTS instances (e.g., Instance A and B) share a source or destination, DTS uses the shortest configured retry duration (e.g., 30 minutes for A, 60 for B, so 30 minutes is used) for all instances. DTS charges for task runtime during connection retries. Set a custom duration based on your business needs, or release the DTS instance promptly after you release the source/destination instances.
      Retry Time for Other Issues	If a non-connection issue (e.g., a DDL or DML execution error) occurs, DTS reports an error and immediately retries the operation. The default retry duration is 10 minutes. You can also customize the retry time to a value from 1 to 1,440 minutes. We recommend a duration of 10 minutes or more. If the related operations succeed within the set retry time, the synchronization task automatically resumes. Otherwise, the task fails. Important The value of Retry Time for Other Issues must be less than that of Retry Time for Failed Connections.
      Enable Throttling for Full Data Synchronization	During full data synchronization, DTS consumes read and write resources from the source and destination databases, which can increase their load. To mitigate pressure on the destination database, you can limit the migration rate by setting Queries per second (QPS) to the source database, RPS of Full Data Migration, and Data migration speed for full migration (MB/s). Note This parameter is available only if Synchronization Types is set to Full Data Synchronization. You can also adjust the rate of full data synchronization when the synchronization instance is running.
      Enable Throttling for Incremental Data Synchronization	You can also limit the incremental synchronization rate to reduce pressure on the destination database by setting RPS of Incremental Data Synchronization and Data synchronization speed for incremental synchronization (MB/s).
      Environment Tag	You can select an environment tag to identify the instance. This is not required in this example.
      Configure ETL	Choose whether to enable the extract, transform, and load (ETL) feature. For more information, see What is ETL? Valid values: Yes: Enables the ETL feature. Enter data processing statements in the code editor. For more information, see Configure ETL in a data migration or data synchronization task. No: Disables the ETL feature.
      Monitoring and Alerting	Choose whether to set up alerts. If the synchronization fails or the latency exceeds the specified threshold, DTS sends a notification to the alert contacts. No: No alerts are configured. Yes: Configures alerts. You must also set the alert threshold and alert contact. For more information, see Configure monitoring and alerting during task configuration.

   3. Click Data Verification to configure a data verification task.

      To use the data verification feature, see Configure data verification.

   4. Optional: After you complete the preceding configurations, click Next: Configure Database and Table Fields to set the Type, Primary Key Column, and Distribution Key for the tables to be synchronized in the destination AnalyticDB for PostgreSQL instance.

      Note

      • This step is available only if you selected Schema Synchronization when you configured the task objects. You can select All for Definition Status to make modifications.

      • You can select multiple columns to form a composite Primary Key Column. You must select one or more of the Primary Key Column to serve as the Distribution Key.

      • For detailed information about primary key columns and distribution columns, see Manage data tables and Table distribution.

6. Save the task and perform a precheck.

   • To view the parameters for configuring this instance via an API operation, hover over the Next: Save Task Settings and Precheck button and click Preview OpenAPI parameters in the tooltip.

   • If you have finished viewing the API parameters, click Next: Save Task Settings and Precheck at the bottom of the page.

   Note

   • Before a synchronization task starts, DTS performs a precheck. You can start the task only if the precheck passes.

   • If the precheck fails, click View Details next to the failed item, fix the issue as prompted, and then rerun the precheck.

   • If the precheck generates warnings:

     • For non-ignorable warning, click View Details next to the item, fix the issue as prompted, and run the precheck again.

     • For ignorable warnings, you can bypass them by clicking Confirm Alert Details, then Ignore, and then OK. Finally, click Precheck Again to skip the warning and run the precheck again. Ignoring precheck warnings may lead to data inconsistencies and other business risks. Proceed with caution.

7. Purchase the instance.

   1. When the Success Rate reaches 100%, click Next: Purchase Instance.

   2. On the Purchase page, select the billing method and link specifications for the data synchronization instance. For more information, see the following table.

      Category	Parameter	Description
      New Instance Class	Billing Method	Subscription: You pay upfront for a specific duration. This is cost-effective for long-term, continuous tasks. Pay-as-you-go: You are billed hourly for actual usage. This is ideal for short-term or test tasks, as you can release the instance at any time to save costs.
      	Resource Group Settings	The resource group to which the instance belongs. The default is default resource group. For more information, see What is Resource Management?.
      	Instance Class	DTS offers synchronization specifications at different performance levels that affect the synchronization rate. Select a specification based on your business requirements. For more information, see Data synchronization link specifications.
      	Subscription Duration	In subscription mode, select the duration and quantity of the instance. Monthly options range from 1 to 9 months. Yearly options include 1, 2, 3, or 5 years. Note This option appears only when the billing method is Subscription.

   3. Read and select the checkbox for Data Transmission Service (Pay-as-you-go) Service Terms.

   4. Click Buy and Start, and then click OK in the OK dialog box.

      You can monitor the task progress on the data synchronization page.