Migrate data from a Db2 for LUW database to an AnalyticDB for PostgreSQL instance

Prerequisites

• The destination AnalyticDB for PostgreSQL instance is created, and the available storage space of the destination AnalyticDB for PostgreSQL instance is larger than the total size of the data in the source Db2 for LUW database. For more information about how to create an AnalyticDB for PostgreSQL instance, see Create an instance.

  Note

  For more information about the supported database versions, see Overview of data migration scenarios.

• A database is created in the destination AnalyticDB for PostgreSQL instance to receive data. For more information, see Import vector data.

• The archive logging feature is enabled for the source Db2 for LUW database for incremental data migration. For more information, see logarchmeth1 - Primary log archive method configuration parameter and logarchmeth2 - Secondary log archive method configuration parameter.

  Important

  After you modify the logarchmeth configurations, you must back up the source database to make the modification take effect. Otherwise, an error may be returned during the precheck.

Limits

Billing rules

SQL operations that can be incrementally migrated

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:

• Db2 for LUW: Creating group and user IDs for a Db2 database installation (Linux and UNIX) and Authorities overview

• AnalyticDB for PostgreSQL: Create a database account and Manage users and permissions

Procedure

1. Go to the Data Migration Tasks page.
   1. Log on to the Data Management (DMS) console.
   2. In the top navigation bar, click DTS.
   3. In the left-side navigation pane, choose DTS (DTS) > Data Migration.
   Note

   • Operations may vary based on the mode and layout of the DMS console. For more information, see Simple mode and Customize the layout and style of the DMS console.
   • You can also go to the Data Migration Tasks page of the new DTS console.
2. From the drop-down list next to Data Migration Tasks, select the region in which the data migration instance resides.
   Note

   If you use the new DTS console, you must select the region in which the data migration instance resides in the upper-left corner.

3. Click Create Task. On the Create Task wizard page, configure the source and destination databases.

   Section	Parameter	Description

   Section	Parameter	Description
   N/A	Task Name	The name of the task. DTS automatically assigns a name to the task. We recommend that you specify a descriptive name that makes it easy to identify the task. You do not need to specify a unique task name.
   Source Database	Select an existing DMS database instance. (Optional. If you have not registered a DMS database instance, ignore this option and configure database settings in the section below.)	The database instance that you want to use. You can choose whether to select 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 select an existing instance, you must manually configure parameters for the database.
   	Database Type	The type of the source database. Select DB2 for LUW.
   	Access Method	The access method of the source database. Set this parameter based on the location in which the source Db2 for LUW database is deployed. In this example, Self-managed Database on ECS is selected. Note If you select another method to access the source self-managed database, prepare the environment accordingly. For more information, see Preparation overview.
   	Instance Region	The region in which the source Db2 for LUW database resides.
   	Replicate Data Across Alibaba Cloud Accounts	Specifies whether to migrate data across Alibaba Cloud accounts. In this example, No is selected.
   	ECS Instance ID	The ID of the Elastic Compute Service (ECS) instance that hosts the source Db2 for LUW database.
   	Port Number	The service port number of the source Db2 for LUW database.
   	Database Name	The name of the source Db2 for LUW database to which the objects to be migrated belong.
   	Database Account	The account of the source Db2 for LUW database. For more information about the permissions that are required for the database account, see the Permissions required for database accounts section of this topic.
   	Database Password	The password of the database account.
   Destination Database	Select an existing DMS database instance. (Optional. If you have not registered a DMS database instance, ignore this option and configure database settings in the section below.)	The database instance that you want to use. You can choose whether to select 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 select an existing instance, you must manually configure parameters for the database.
   	Database Type	The type of the destination database. Select AnalyticDB for PostgreSQL.
   	Access Method	The access method of the destination database. Select Alibaba Cloud Instance.
   	Instance Region	The region in which the destination AnalyticDB for PostgreSQL instance resides.
   	Instance ID	The ID of the destination AnalyticDB for PostgreSQL instance.
   	Database Name	The name of the database that is used to receive the objects to be migrated in the destination AnalyticDB for PostgreSQL instance.
   	Database Account	The database account of the destination AnalyticDB for PostgreSQL instance. For information about the permissions that are required for the account, see the Permissions required for database accounts section of this topic.
   	Database Password	The password of the database account.

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

   If the source or destination database is an Alibaba Cloud database instance, such as an ApsaraDB RDS for MySQL or ApsaraDB for MongoDB instance, DTS automatically adds the CIDR blocks of DTS servers to the IP address whitelist of the instance. If the source or destination database is a self-managed database hosted on an Elastic Compute Service (ECS) instance, DTS automatically adds the CIDR blocks of DTS servers to the security group rules of the ECS instance, and you must make sure that the ECS instance can access the database. If the self-managed database is hosted on multiple ECS instances, you must manually add the CIDR blocks of DTS servers to the security group rules of each ECS instance. If the source or destination database is a self-managed database that is deployed in a data center or provided by a third-party cloud service provider, you must manually add the CIDR blocks of DTS servers to the IP address whitelist of the database to allow DTS to access the database. For more information, see the "CIDR blocks of DTS servers" section of the Add the CIDR blocks of DTS servers to the security settings of on-premises databases topic.

   Warning

   If the public CIDR blocks of DTS servers are automatically or manually added to the IP address whitelist of a database instance or to the security group rules of an ECS instance, security risks may arise. Therefore, 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 account and password, limiting the ports that are exposed, authenticating API calls, regularly checking the IP address whitelist or ECS security group rules and forbidding unauthorized CIDR blocks, and connecting the database to DTS by using Express Connect, VPN Gateway, or Smart Access Gateway.

5. Configure the objects to be migrated and advanced settings.

   Parameter	Description

   Parameter	Description
   Migration Types	To perform only full data migration, select Schema Migration and Full Data Migration. To ensure service continuity during data migration, select Schema Migration, 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.
   DDL and DML Operations to Be Synchronized	Select the SQL operations that you want to incrementally migrate. For more information, see the SQL operations that can be incrementally migrated section of this topic. Note To select the SQL operations performed on a specific database or table, perform the following steps: In the Selected Objects section, right-click an object. In the dialog box that appears, select the SQL operations that you want to incrementally migrate.
   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 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 You can use the object name mapping feature to rename the tables that are migrated to the destination database. You can use this feature if the source and destination databases contain tables that have 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 inconsistency may occur and your business may be exposed to the following potential risks: If the source and destination databases have the same schemas, DTS does not migrate data records that have the same primary key values as data records in the destination database. 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 in the source or destination database. For more information, see Specify the capitalization of object names in the destination instance. Important We recommend that you specify a policy that is consistent with the default policy of the destination database, such as lowercase. Otherwise, an error may be reported when the task is in progress.
   Source Objects	Select one or more objects from the Source Objects section and click the icon to add the objects to the Selected Objects section. Note You can select only tables as the objects to be migrated.
   Selected Objects	To rename an object that you want to migrate 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. Note If you use the object name mapping feature, data may be inconsistent or other objects that depend on this object may fail to be migrated. For example, if column mapping is used for non-full table migration or if the schemas of the source and destination tables are inconsistent, the data in the columns of the source database that are not contained in the destination database is lost. To specify WHERE conditions to filter data, right-click an object in the Selected Objects section. In the dialog box that appears, specify the conditions. For more information, see Use SQL conditions to filter data. To incrementally migrate the SQL operations that are 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 incrementally migrate. For more information about the SQL statements that can be incrementally migrated, see the SQL operations that can be incrementally migrated section of this topic.

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

   • Data Verification Settings

     For more information about how to configure the data verification feature, see Enable data verification.

   • Advanced Settings

     Parameter	Description

     Parameter	Description
     Select the dedicated cluster used to schedule the task	By default, DTS schedules the data migration task to the shared cluster if you do not specify a dedicated cluster. You can also purchase and specify a dedicated cluster of the required specifications to run the data migration task. For more information, see What is a DTS dedicated cluster.
     Set Alerts	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 will receive notifications. Valid values: No: does not configure alerting. Yes: configures alerting. If you select Yes, you must also specify the alert threshold and alert contacts. For more information, see Configure monitoring and alerting.
     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 your earliest opportunity after the source and destination instances are released.
     The wait time before a retry when other issues occur in the source and destination databases.	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 The wait time before a retry when other issues occur in the source and destination databases 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 This parameter is displayed only when Full Data Migration is selected as Migration Types.
     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 This parameter is displayed only when Incremental Data Migration is selected as Migration Types.
     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 configure 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.

7. Optional. Click Next: Configure Database and Table Fields to specify the Type, Primary Key Column, and Distribution Key parameters for the tables that you want to migrate to the AnalyticDB for PostgreSQL instance.

   Note

   • This step is required only if you select Schema Migration when you configure the objects to be migrated for the task. You can set the Definition Status parameter to All and modify the database and table fields.

   • In the Primary Key Column field, you can specify multiple columns to form a composite primary key. In this case, you must specify one or more primary key columns as the distribution key columns.

   • For more information about primary key columns and distribution key columns, see Manage tables and Define table distribution.

8. 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 troubleshoot the issues based on the error message, you can run a precheck again.

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

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

9. Wait until the success rate becomes 100%. Then, click Next: Purchase Instance.

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

    Section	Parameter	Description

    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 Specifications of data migration instances.

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

12. Click Buy and Start to start the data migration task. You can view the progress of the task in the task list.