Migrate data between PolarDB for PostgreSQL (Compatible with Oracle) clusters - Data Transmission Service

This topic describes how to migrate data between PolarDB for PostgreSQL (Compatible with Oracle) clusters by using Data Transmission Service (DTS).

Prerequisites

The source and destination PolarDB for PostgreSQL (Compatible with Oracle) clusters are created. For more information, see Create a cluster.
In the source PolarDB for PostgreSQL (Compatible with Oracle) cluster, the wal_level parameter is set to logical. This indicates that the information required for logical encoding is added to the write-ahead logging (WAL) logs. For more information, see Configure cluster parameters.

Usage notes

Note

During schema migration, DTS migrates foreign keys from the source database to the destination database.
During full data migration and incremental data migration, DTS temporarily disables the constraint check and cascade operations on foreign keys at the session level. If you perform the cascade update and delete operations on the source database during data migration, data inconsistency may occur.

Category	Description
Limits on the source database	The server to which the source database belongs must have sufficient outbound bandwidth. Otherwise, the data migration speed decreases. The tables to be migrated must have PRIMARY KEY or UNIQUE constraints and all fields must be unique. Otherwise, the destination database may contain duplicate data records. If you select tables as objects that you want to migrate and you need to edit tables, such as renaming tables or columns in the destination database, up to 1,000 tables can be migrated in a single data migration task. If you run a task to migrate more than 1,000 tables, a request error occurs. In this case, we recommend that you configure multiple tasks to migrate the tables or configure a task to migrate the entire database. If you need to migrate incremental data, make sure that the following requirements are met: The write-ahead logging (WAL) feature must be enabled. For incremental data migration, the WAL logs of the source database must be stored for more than 24 hours. For full data and incremental data migration, the WAL logs of the source database must be stored for at least seven days. Otherwise, DTS may fail to obtain the WAL logs and the task may fail. In exceptional circumstances, data inconsistency or loss may occur. After full data migration is complete, you can set the retention period to more than 24 hours. Make sure that you set the retention period of WAL logs based on the preceding requirements. Otherwise, the service reliability and performance stated in the Service Level Agreement (SLA) of DTS may not be guaranteed. Limits on operations to be performed on the source database: During schema migration and full data migration, do not perform DDL operations to change the schemas of databases or tables. Otherwise, the data migration task fails. If you perform only full data migration, do not write data to the source database during data migration. Otherwise, data inconsistency between the source and destination databases occurs. To ensure data consistency, we recommend that you select Schema Migration, Full Data Migration, and Incremental Data Migration as the migration types. If you want to perform a primary/secondary switchover on the source PolarDB for PostgreSQL(Compatible with Oracle) cluster, the Logical Replication Slot Failover feature must be enabled. This prevents logical subscriptions from being interrupted and ensures that your data synchronization task can run as expected. For more information, see Logical replication slot failover. If one or more long-running transactions exist in the source database and incremental data is migrated in the data migration task, the WAL logs generated before the long-running transactions in the source database are committed may be accumulated. As a result, the disk space of the source database may be insufficient.
Other limits	A data migration task can migrate data from only a single database. To migrate data from multiple databases, you must create a data migration task for each database. During incremental data migration, if you select a schema as the object to be migrated, take note of the following limits: If you create a table in the schema or run the RENAME command to rename the table, you must execute the `ALTER TABLE schema.table REPLICA IDENTITY FULL;` statement before you write data to the table. Note Replace the `schema` and `table` in the preceding sample statement with the actual schema name and table name. To ensure the accuracy of the displayed latency during incremental data migration, DTS creates a table named `dts_postgres_heartbeat` in the source database. The following figure shows the structure and content of the table. During incremental data migration, DTS creates a replication slot for the source database. The replication slot is prefixed with `dts_sync_`. DTS can obtain the incremental logs of the source database within the last 15 minutes by using this replication slot. Note After the DTS instance is released, the replication slot is automatically deleted. If you change the password of the source database or delete the IP address whitelist of DTS, the replication slot cannot be automatically deleted. In that case, you must manually delete the replication slot from the source database to prevent the replication slot from piling up. If the data migration task is released or fails, DTS automatically clears the replication slot. If a primary/secondary switchover is performed on the source cluster, you must log on to the secondary instance to clear the replication slot. Before you migrate data, evaluate the impact of data migration on the performance of the source and destination databases. We recommend that you migrate data during off-peak hours. During full data migration, DTS uses the read and write resources of the source and destination databases. This may increase the loads on the database servers. During full data migration, concurrent INSERT operations cause fragmentation in the tables of the destination database. After full data migration is complete, the tablespace of the destination database is larger than that of the source database. Make sure that the precision settings for columns of the FLOAT or DOUBLE data type meet your business requirements. DTS uses the `ROUND(COLUMN,PRECISION)` function to retrieve values from columns of the FLOAT or DOUBLE data type. If you do not specify a precision, DTS sets the precision for the FLOAT data type to 38 digits and the precision for the DOUBLE data type to 308 digits. DTS attempts to resume data migration tasks that failed within the last seven days. Before you switch workloads to the destination database, you must stop or release the failed tasks. You can also execute the `REVOKE` statement to revoke the write permissions from the accounts that are used by DTS to access the destination database. Otherwise, the data in the source database overwrites the data in the destination database after the failed task is resumed. DTS does not check the validity of metadata such as sequences. You must manually check the validity of metadata. After your workloads are switched to the destination database, newly written sequences do not increment from the maximum value of the sequences in the source database. Therefore, you must query the maximum value of the sequences in the source database before you switch your workloads to the destination database. Then, you must specify the queried maximum value as the initial value of the sequences in the destination database. You can execute the following statements to query the maximum value of the sequences in the source database: `do language plpgsql $$ declare nsp name; rel name; val int8; begin for nsp,rel in select nspname,relname from pg_class t2 , pg_namespace t3 where t2.relnamespace=t3.oid and t2.relkind='S' loop execute format($_$select last_value from %I.%I$_$, nsp, rel) into val; raise notice '%', format($_$select setval('%I.%I'::regclass, %s);$_$, nsp, rel, val+1); end loop; end; $$;`

Billing

Migration type	Instance configuration fee	Internet traffic fee
Schema migration and full data migration	Free of charge.	Charged only when data is migrated from Alibaba Cloud over the Internet. For more information, see Billing overview.
Incremental data migration	Charged. For more information, see Billing overview.

Migration types

Migration type	Description
Schema migration	DTS migrates the schemas of objects to the destination database. DTS supports schema migration for the following types of objects: table, view, synonym, trigger, stored procedure, stored function, package, and user-defined type. Note In this scenario, DTS does not support schema migration for triggers. We recommend that you delete the triggers of the source database to prevent data inconsistency caused by the triggers. For more information, see Configure a data synchronization or migration task for a source database that contains a trigger.
Full data migration	DTS migrates the historical data of objects from the source database to the destination database. Note During schema migration and full data migration, we recommend that you do not perform DDL operations on the objects to be migrated. Otherwise, the data migration task may fail.
Incremental data migration	DTS retrieves redo log files from the source database. Then, DTS migrates incremental data from the source database to the destination database. Incremental data migration allows you to ensure service continuity when you migrate data.

SQL operations that support incremental migration

Operation type	SQL statement
DML	INSERT, UPDATE, and DELETE
DDL	DDL operations can be migrated only in the data migration tasks that are created after October 1, 2020. Important If a data migration task is created before May 12, 2023, you must create a trigger and a function in the source database to capture DDL information before you configure the data migration task. For more information, see Use triggers and functions to implement incremental DDL migration for PostgreSQL databases. You cannot migrate data of the BIT type during incremental data migration. If the account of the source database is a privileged account, DTS can migrate the following DDL statements: CREATE TABLE and DROP TABLE ALTER TABLE, including RENAME TABLE, ADD COLUMN, ADD COLUMN DEFAULT, ALTER COLUMN TYPE, DROP COLUMN, ADD CONSTRAINT, ADD CONSTRAINT CHECK, and ALTER COLUMN DROP DEFAULT TRUNCATE TABLE CREATE INDEX ON TABLE Important You cannot migrate additional information of DDL statements, such as CASCADE or RESTRICT. You cannot migrate DDL statements from a session in which the `SET session_replication_role = replica` statement is executed. You cannot migrate DDL statements that are executed by invoking functions. If the SQL statements submitted by the source database at a time contain both DML and DDL statements, DTS does not migrate the DDL statements. If the SQL statements submitted by the source database at a time contain DDL statements that are not to be migrated, DTS does not migrate the DDL statements.

Permissions required for database accounts

Database type	Required permissions
Source PolarDB for PostgreSQL (Compatible with Oracle) cluster	Permissions of a privileged account
Destination PolarDB for PostgreSQL (Compatible with Oracle) cluster	Permissions of the database owner Important The database owner is specified when you create the database.

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

PolarDB for PostgreSQL (compatible with Oracle) cluster: Create database accounts

Procedure

Go to the Data Migration Tasks page.
1. Log on to the Data Management (DMS) console.
2. In the top navigation bar, move the pointer over DTS.
3. Choose DTS (DTS) > Data Migration.
Note
- The actual 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 page of the new DTS console.
From the drop-down list on the right side of Data Migration Tasks, select the region in which your 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.

Click Create Task. On the Create Data Migration Task page, configure the source and destination databases. The following table describes the parameters.

Warning

After you configure the source and destination databases, we recommend that you read the Limits that are displayed in the upper part of the page. Otherwise, the task may fail or data inconsistency may occur.

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 an existing DMS database instance	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 select an existing instance, you must configure parameters for the source database.
	Database Type	The type of the source database. Select PolarDB (Compatible with Oracle).
	Access Method	The access method of the source database. Select Public IP Address.
	Instance Region	The region in which the source PolarDB for PostgreSQL (Compatible with Oracle) cluster resides.
	Data Sources	Single Data Source: If you select this option, you must configure the Domain Name or IP Address and Port Number parameters of the primary node in the source PolarDB for PostgreSQL (Compatible with Oracle) cluster. Multiple Data Sources: If you select this option, you must specify the IP addresses and port numbers of multiple nodes, including the primary node, in the source PolarDB for PostgreSQL (Compatible with Oracle) cluster in the IP:Port of Data Sources field. Note If you select Multiple Data Sources and configure the IP:Port of Data Sources parameter, DTS can automatically switch to a new primary node in the PolarDB for PostgreSQL (Compatible with Oracle) cluster during primary/secondary switchover. This is suitable for scenarios such as disaster recovery. In this example, Single Data Source is selected.
	Domain Name or IP Address	The endpoint of the primary node in the source PolarDB for PostgreSQL (Compatible with Oracle) cluster. Note You can run the ping command on your computer to obtain the IP address that is used to access the source PolarDB for PostgreSQL (Compatible with Oracle) cluster.
	Port Number	The service port number of the source database. Default value: 1521. Note In this example, the service port of the source database must be accessible over the Internet.
	IP:Port of Data Sources	The IP addresses and port numbers of multiple nodes, including the primary node, in the source PolarDB for PostgreSQL (Compatible with Oracle) cluster. Specify each value in the IP address:Port number format. Separate multiple values with commas (,).
	Oracle Type	The architecture of the source database. If you select Non-RAC Instance, you must configure the SID parameter. If you select RAC or PDB Instance, you must configure the Service Name parameter. In this example, Non-RAC Instance is selected.
	Database Name	The name of the database that contains the objects to be migrated from the source PolarDB for PostgreSQL (compatible with Oracle) cluster.
	Database Account	The database account of the source PolarDB for PostgreSQL (Compatible with Oracle) cluster. 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 that is used to access the database instance.
Destination Database	Select an existing DMS database instance	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 instance. If you do not select an existing instance, you must configure parameters for the destination database.
	Database Type	The type of the destination database. Select PolarDB (Compatible with Oracle).
	Access Method	The access method of the destination database. Select Public IP Address.
	Instance Region	The region in which the destination PolarDB for PostgreSQL (Compatible with Oracle) cluster resides.
	Data Sources	Single Data Source: If you select this option, you must configure the Domain Name or IP Address and Port Number parameters of the primary node in the destination PolarDB for PostgreSQL (Compatible with Oracle) cluster. Multiple Data Sources: If you select this option, you must specify the IP addresses and port numbers of multiple nodes, including the primary node, in the destination PolarDB for PostgreSQL (Compatible with Oracle) cluster in the IP:Port of Data Sources field. Note If you select Multiple Data Sources and configure the IP:Port of Data Sources parameter, DTS can automatically switch to a new primary node in the PolarDB for PostgreSQL (Compatible with Oracle) cluster during primary/secondary switchover. This is suitable for scenarios such as disaster recovery. In this example, Single Data Source is selected.
	Domain Name or IP Address	The endpoint of the primary node in the destination PolarDB for PostgreSQL (Compatible with Oracle) cluster. Note You can run the ping command on your computer to obtain the IP address that is used to access the destination PolarDB for PostgreSQL (Compatible with Oracle) cluster.
	Port Number	The service port number of the destination database. Default value: 1521.
	IP:Port of Data Sources	The IP addresses and port numbers of multiple nodes, including the primary node, in the destination PolarDB for PostgreSQL (Compatible with Oracle) cluster. Specify each value in the IP address:Port number format. Separate multiple values with commas (,).
	Database Name	The name of the database to which objects are migrated in the destination PolarDB for PostgreSQL (Compatible with Oracle) cluster.
	Database Account	The database account of the destination PolarDB for PostgreSQL (Compatible with Oracle) cluster. 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 that is used to access the database instance.

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

Configure the objects to be migrated and advanced settings. The following table describes the parameters.

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.
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.
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 schemas 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 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 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 an object in the Selected Objects section. In the dialog box that appears, select the SQL operations that you want to migrate. For more information about the SQL operations that support incremental migration, see the SQL operations that support incremental migration section of this topic.

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 change tracking 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 Configure monitoring and alerting when you create a DTS task.

In the lower part of the page, click Next: Save Task Settings and Precheck.
You can move the pointer over Next: Save Task Settings and Precheck and click Preview OpenAPI parameters to view the parameters to be specified when you call the relevant API operation to configure the DTS task.
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.
Wait until Success Rate becomes 100%. Then, click Next: Purchase Instance.

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 Settings	The resource group to which the data migration instance belongs. Default value: default resource group. For more information, see What is Resource Management?
New Instance Class	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.

Read and agree to Data Transmission Service (Pay-as-you-go) Service Terms by selecting the check box.
Click Buy and Start. In the dialog box that appears, click OK.
You can view the progress of the task in the task list.