Migrate data from an ApsaraDB RDS for PPAS instance to a PolarDB-O cluster

Prerequisites

• A PolarDB-O cluster is created. For more information, see Create a PolarDB-O cluster.
• The available storage space of the PolarDB-O cluster is larger than the total size of the data in the ApsaraDB RDS for PPAS instance.
• To migrate incremental data from an ApsaraDB RDS for PPAS instance, you must submit a ticket to grant the superuser permission to the database account.

Precautions

• DTS uses read and write resources of the source and destination databases during full data migration. This may increase the loads of the database servers. If the database performance is unfavorable, the specification is low, or the data volume is large, database services may become unavailable. For example, DTS occupies a large amount of read and write resources in the following cases: a large number of slow SQL queries are performed on the source database, the tables have no primary keys, or a deadlock occurs in the destination database. 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. For example, you can migrate data when the CPU utilization of the source and destination databases is less than 30%.
• The tables to be migrated in the source database must have PRIMARY KEY or UNIQUE constraints and all fields must be unique. Otherwise, the destination database may contain duplicate data records.
• A single data migration task can migrate data from only one database. To migrate data from multiple databases, you must create a data migration task for each database.
• If a data migration task fails, DTS automatically resumes the task. Before you switch your workloads to the destination instance, stop or release the data migration task. Otherwise, the data in the source database will overwrite the data in the destination instance after the task is resumed.
• 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 starting value of the sequences in the destination database. You can run 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;
  $$;

Migration types

Billing

Permissions required for database accounts

Log on to the source Oracle database, create an account for data collection, and grant permissions to the account.

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

• ApsaraDB RDS for PPAS instance: Create an account on an ApsaraDB RDS for PPAS instance
  Notice To migrate incremental data from an ApsaraDB RDS for PPAS database, you must submit a ticket to grant the superuser permission to the database account.
• PolarDB-O cluster: Create database accounts

Procedure

1. Log on to the DTS console.
2. In the left-side navigation pane, click Data Migration.
3. At the top of the Migration Tasks page, select the region where the destination cluster resides.
   
4. In the upper-right corner of the page, click Create Migration Task.
5. 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 for easy identification. You do not need to use a unique task name.
   Source Database	Instance Type	Select User-Created Database with Public IP Address. You cannot select ApsaraDB RDS for PPAS as the instance type.
   	Instance Region	If the instance type is set to User-Created Database with Public IP Address, you do not need to specify the instance region. Note You can click Get IP Address Segment of DTS to obtain the CIDR blocks of DTS servers. Then, you can add the CIDR blocks of DTS servers to the whitelist of the ApsaraDB RDS for PPAS instance. For more information, see Configure an IP address whitelist for an ApsaraDB RDS for PPAS instance.
   	Database Type	Select PPAS.
   	Version	Select the database engine version of the ApsaraDB RDS for PPAS instance.
   	Hostname or IP Address	Enter the public endpoint of the ApsaraDB RDS for PPAS instance.
   	Port Number	Enter the service port number of the ApsaraDB RDS for PPAS instance. The default port number is 3433.
   	Database Name	Enter the name of the source database in the ApsaraDB RDS for PPAS instance.
   	Database Account	Enter the database account of the ApsaraDB RDS for PPAS instance. For more information about the permissions that are required for the database account, see Permissions required for database accounts.
   	Database Password	Enter the password of the database account. Note After you specify the source database parameters, click Test Connectivity next to Database Password to verify whether the specified parameters are valid. If the specified parameters are valid, the Passed message appears. If the Failed message appears, click Check next to Failed. Modify the source database parameters based on the check results.
   Destination Database	Instance Type	Select PolarDB.
   	Instance Region	Select the region where the destination PolarDB-O cluster resides.
   	PolarDB Instance ID	Select the ID of the destination PolarDB-O cluster resides.
   	Database Name	Enter the name of the destination database.
   	Database Account	Enter the database account of the destination PolarDB-O cluster. For more information about the permissions that are required for the database account, see Permissions required for database accounts.
   	Database Password	Enter the password of the database account. Note After you specify the destination database parameters, click Test Connectivity next to Database Password to verify whether the parameters are valid. If the specified parameters are valid, the Passed message appears. If the Failed message appears, click Check next to Failed. Modify the destination database parameters based on the check results.

6. In the lower-right corner of the page, click Set Whitelist and Next.
   Note DTS adds the CIDR blocks of DTS servers to the whitelists of the destination PolarDB-O cluster. This ensures that DTS servers can connect to the destination PolarDB-O cluster.
7. Select the migration types and the objects to be migrated.
   

   Setting	Description
   Select the 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. Notice If Incremental Data Migration is not selected, we recommend that you do not write data to the source database during schema migration or full data migration. This ensures data consistency between the source and destination databases. During schema migration and full data migration, we recommend that you do not perform DDL operations on the required objects. Otherwise, the objects may fail to be migrated.
   Select the objects to be migrated	Select one or more objects from the Available section and click the icon to move the objects to the Selected section. Note You can select columns, tables, or databases as the objects to be migrated. By default, after an object is migrated to the destination database, the name of the object remains unchanged. You can use the object name mapping feature to rename the objects that are migrated to the destination database. For more information, see Object name mapping. 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.
   Specify whether to rename objects	You can use the object name mapping feature to rename the objects that are migrated to the destination instance. For more information, see Object name mapping.
   Specify the retry time for failed connections to the source or destination database	By default, if DTS fails to connect to the source or destination database, DTS retries within the next 12 hours. You can specify the retry time based on your needs. If DTS reconnects to the source and destination databases within the specified time, DTS resumes the data migration task. Otherwise, the data migration task fails. Note 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.

8. In the lower-right corner of the page, click Precheck.
   Note

   • Before you can start the data migration task, a precheck is performed. You can start the data migration 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.
9. After the task passes the precheck, click Next.
10. In the Confirm Settings dialog box, specify the Channel Specification parameter and select Data Transmission Service (Pay-As-You-Go) Service Terms.
11. Click Buy and Start to start the data migration task.
    • Schema migration and full data migration

      We recommend that you do not manually stop the task during full data migration. Otherwise, the data migrated to the destination database will be incomplete. You can wait until the data migration task automatically stops.

    • Schema migration, full data migration, and incremental data migration

      The task does not automatically stop during incremental data migration. You must manually stop the task.

      Notice We recommend that you select an appropriate time to manually stop the data migration task. For example, you can stop the task during off-peak hours or before you switch your workloads to the destination cluster.
      1. Wait until Incremental Data Migration and The migration task is not delayed appear in the progress bar of the migration task. Then, stop writing data to the source database for a few minutes. The delay time of incremental data migration may be displayed in the progress bar.
      2. Wait until the status of incremental data migration changes to The migration task is not delayed again. Then, manually stop the migration task.