All Products
Search
Document Center

PolarDB:Migrate data from a self-managed Oracle database to a PolarDB for PostgreSQL (Compatible with Oracle) cluster

Last Updated:Mar 11, 2024

This topic describes how to migrate data from a self-managed Oracle database to a PolarDB for PostgreSQL (Compatible with Oracle) cluster by using Data Transmission Service (DTS).

Prerequisites

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 and delete operations on the source database during data migration, data inconsistency may occur.

Category

Description

Limits on the source database

  • Bandwidth requirements: The server to which the source database belongs must have sufficient outbound bandwidth. Otherwise, the data migration speed decreases.

  • If the source database is an Oracle Real Application Cluster (RAC) database connected over Express Connect, you must specify a virtual IP address (VIP) for the database when you configure the source database information.

  • If the source database is an Oracle RAC database connected over Express Connect, VPN Gateway, Smart Access Gateway, Database Gateway, or Cloud Enterprise Network (CEN), you can use a single VIP rather than a Single Client Access Name (SCAN) IP address when you configure the source database information. After you specify the VIP, node failover is not supported for the Oracle RAC database.

  • If a field in the source Oracle database contains an empty string of the VARCHAR2 type, which is evaluated as null in the Oracle database, and the corresponding field in the destination database has a NOT NULL constraint, the migration task fails.

  • Requirements for the objects to migrate:

    • 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 the version of your Oracle database is 12c or later, the names of the tables to be migrated cannot exceed 30 bytes in length.

    • If you select tables as the objects to be migrated and you need to modify the tables in the destination database, such as renaming tables or columns, 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 split the tables and configure multiple tasks to migrate the tables, or configure a task to migrate the entire database.

  • If you want to migrate incremental data, you must make sure that the following requirements are met:

    • The redo logging and archive logging must be enabled.

    • If you perform only incremental data migration, the redo logs and archive logs of the source database must be stored for more than 24 hours. If you perform both full data migration and incremental data migration, the redo logs and archive logs of the source database must be stored for at least seven days. After full data migration is complete, you can set the retention period to more than 24 hours. Otherwise, DTS may fail to obtain the redo logs and archive logs and the task may fail. In extreme cases, data may be inconsistent or lost. Make sure that you set the retention period of redo logs and archive 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 data definition language (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 may occur. To ensure data consistency, we recommend that you select Schema Migration, Full Data Migration, and Incremental Data Migration as the migration types.

    • During data migration, do not update LONGTEXT fields. Otherwise, the data migration task fails.

Other limits

  • Before you migrate data, evaluate the impact of data migration on the performance of the source database and destination cluster. We recommend that you migrate data during off-peak hours. During full data migration, DTS uses the read and write resources of the source database and destination cluster. This may increase the loads on the database servers.

  • During full data migration, concurrent INSERT operations cause fragmentation in the tables of the destination cluster. After full data migration is complete, the size of used tablespace of the destination cluster is larger than that of the source database.

  • DTS attempts to resume data migration tasks that failed within the last seven days. Before you switch workloads to the destination cluster, 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.

  • Because the destination PolarDB for PostgreSQL (Compatible with Oracle) cluster generates unique indexes like pg_oid_1498503_index to correspond to ROWID of the self-managed Oracle database, the indexes of the destination PolarDB for PostgreSQL (Compatible with Oracle) cluster is more than that of the source self-managed Oracle database.

  • When CHECK constraints created in the source Oracle database are migrated to the destination PolarDB for PostgreSQL (Compatible with Oracle) cluster, they will be converted to NOT NULL constraints.

  • Objects of the custom types can be migrated to the destination PolarDB for PostgreSQL (Compatible with Oracle) cluster. However, the objects that are automatically generated by the source Oracle database (also known as built-in objects) cannot be migrated.

    Note

    The PolarDB for PostgreSQL (Compatible with Oracle) cluster already supports the built-in objects in the Oracle database. You do not need to manually migrate data.

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 type

Migration Type

Description

Schema migration

DTS migrates the schemas of the required objects to the destination PolarDB for PostgreSQL (compatible with Oracle) cluster. 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 triggers. For more information, see Configure a data synchronization task for a source database that contains a trigger.

Full data migration

DTS migrates all the historical data of required objects from the self-managed Oracle database to the PolarDB for PostgreSQL (compatible with Oracle) cluster.

Note

During schema migration and full data migration, do not perform DDL operations on the objects to be migrated. Otherwise, the objects may fail to be migrated.

Incremental data migration

After full data migration is complete, DTS retrieves redo log files from the self-managed Oracle database. Then, DTS migrates incremental data from the self-managed Oracle database to the destination PolarDB for PostgreSQL (compatible with Oracle) cluster.

Incremental data migration ensures service continuity of self-managed applications during data migration.

Data type mappings

For more information, see Data type mappings between heterogeneous databases.

SQL operations that can be incrementally migrated

Operation type

SQL statement

DML

INSERT, UPDATE, and DELETE

DDL

  • CREATE TABLE

    Note

    If a CREATE TABLE statement contains partitioning clauses, subpartitioning clauses, or functions, DTS does not migrate the statement. In addition, DTS does not migrate the CREATE TABLE AS SELECT statements.

  • ALTER TABLE, including ADD COLUMN, ADD INDEX, DROP COLUMN, DROP INDEX, MODIFY COLUMN, and RENAME COLUMN

  • DROP TABLE

  • RENAME TABLE, TRUNCATE TABLE, and CREATE INDEX

Preparations

Log on to the self-managed Oracle database, create an account that you want to use to collect data, and then grant permissions to the account.

Note

If you have created an account that is granted the permissions listed in the following table, you can skip this step.

Database

Schema migration

Full data migration

Incremental data migration

Self-managed Oracle database

Permissions of the schema owner

Permissions of the schema owner

DBA

PolarDB for PostgreSQL (Compatible with Oracle) cluster

Permissions of the schema owner

To create a database account and grant permissions to the database account, perform the following operations:

Important

If you need to migrate incremental data from an Oracle database but the database administrator (DBA) permissions cannot be granted to the database account, you can enable archive logging and supplemental logging, and grant fine-grained permissions to the account.

  1. Enable archive logging and supplemental logging.

    Type

    Procedure

    Archive logging

    Execute the following statements to enable archive logging:

    shutdown immediate;
    startup mount;
    alter database archivelog;
    alter database open;
    archive log list;

    Supplemental logging

    Enable supplemental logging at the database or table level based on your business requirements.

    Note

    You can enable database-level supplemental logging to ensure the stability of Data Transmission Service (DTS) tasks. You can enable table-level supplemental logging to reduce the disk usage of the source Oracle database.

    • Enable database-level supplemental logging

      1. Execute the following statement to enable minimal supplemental logging:

        alter database add supplemental log data;
      2. Execute the following statement to enable primary key and unique key supplemental logging at the database level:

        alter database add supplemental log data (primary key,unique index) columns;
    • Enable table-level supplemental logging

      1. Execute the following statement to enable minimal supplemental logging:

        alter database add supplemental log data;
      2. Enable table-level supplemental logging by using one of the following methods:

        • Enable primary key supplemental logging at the table level

          alter table table_name add supplemental log data (primary key) columns;
        • Enable table-level supplemental logging for all columns

          alter table tb_name add supplemental log data (all) columns;

    Force logging

    Execute the following statement to enable force logging:

    alter database force logging;
  2. Grant fine-grained permissions to an Oracle database account.

    # Create a database account named rdsdt_dtsacct and grant permissions to the account.
    create user rdsdt_dtsacct IDENTIFIED BY rdsdt_dtsacct;
    grant create session to rdsdt_dtsacct;
    grant connect to rdsdt_dtsacct;
    grant resource to rdsdt_dtsacct;
    grant execute on sys.dbms_logmnr to rdsdt_dtsacct;
    grant select on V_$LOGMNR_LOGS to rdsdt_dtsacct;
    grant select on  all_objects to rdsdt_dtsacct;
    grant select on  all_tab_cols to rdsdt_dtsacct;
    grant select on  dba_registry to rdsdt_dtsacct;
    grant select any table to rdsdt_dtsacct;
    grant select any transaction to rdsdt_dtsacct;
    -- v$log privileges
    grant select on v_$log to rdsdt_dtsacct;
    -- v$logfile privileges
    grant select on v_$logfile to rdsdt_dtsacct;
    -- v$archived_log privileges
    grant select on v_$archived_log to rdsdt_dtsacct;
    -- v$parameter privileges
    grant select on v_$parameter to rdsdt_dtsacct;
    -- v$database privileges
    grant select on v_$database to rdsdt_dtsacct;
    -- v$active_instances privileges
    grant select on v_$active_instances to rdsdt_dtsacct;
    -- v$instance privileges
    grant select on v_$instance to rdsdt_dtsacct;
    -- v$logmnr_contents privileges
    grant select on v_$logmnr_contents to rdsdt_dtsacct;
    -- system tables
    grant select on sys.USER$ to rdsdt_dtsacct;
    grant select on SYS.OBJ$ to rdsdt_dtsacct;
    grant select on SYS.COL$ to rdsdt_dtsacct;
    grant select on SYS.IND$ to rdsdt_dtsacct;
    grant select on SYS.ICOL$ to rdsdt_dtsacct;
    grant select on SYS.CDEF$ to rdsdt_dtsacct;
    grant select on SYS.CCOL$ to rdsdt_dtsacct;
    grant select on SYS.TABPART$ to rdsdt_dtsacct;
    grant select on SYS.TABSUBPART$ to rdsdt_dtsacct;
    grant select on SYS.TABCOMPART$ to rdsdt_dtsacct;
    grant select_catalog_role TO rdsdt_dtsacct;
    
    # Switch to the pluggable database (PDB). Create a database account named rdsdt_dtsacct and grant permissions to the account.
    ALTER SESSION SET container = ORCLPDB1;
    create user rdsdt_dtsacct IDENTIFIED BY rdsdt_dtsacct;
    grant create  session to rdsdt_dtsacct;
    grant connect  to rdsdt_dtsacct;
    grant resource to rdsdt_dtsacct;
    grant execute on sys.dbms_logmnr to rdsdt_dtsacct;
    grant select on  all_objects to rdsdt_dtsacct;
    grant select on  all_tab_cols to rdsdt_dtsacct;
    grant select on  dba_registry to rdsdt_dtsacct;
    grant select any table to rdsdt_dtsacct;
    grant select any transaction to rdsdt_dtsacct;
    -- v$log privileges
    grant select on v_$log to rdsdt_dtsacct;
    -- v$logfile privileges
    grant select on v_$logfile to rdsdt_dtsacct;
    -- v$archived_log privileges
    grant select on v_$archived_log to rdsdt_dtsacct;
    -- v$parameter privileges
    grant select on v_$parameter to rdsdt_dtsacct;
    -- v$database privileges
    grant select on v_$database to rdsdt_dtsacct;
    -- v$active_instances privileges
    grant select on v_$active_instances to rdsdt_dtsacct;
    -- v$instance privileges
    grant select on v_$instance to rdsdt_dtsacct;
    -- v$logmnr_contents privileges
    grant select on v_$logmnr_contents to rdsdt_dtsacct;
    grant select on sys.USER$ to rdsdt_dtsacct;
    grant select on SYS.OBJ$ to rdsdt_dtsacct;
    grant select on SYS.COL$ to rdsdt_dtsacct;
    grant select on SYS.IND$ to rdsdt_dtsacct;
    grant select on SYS.ICOL$ to rdsdt_dtsacct;
    grant select on SYS.CDEF$ to rdsdt_dtsacct;
    grant select on SYS.CCOL$ to rdsdt_dtsacct;
    grant select on SYS.TABPART$ to rdsdt_dtsacct;
    grant select on SYS.TABSUBPART$ to rdsdt_dtsacct;
    grant select on SYS.TABCOMPART$ to rdsdt_dtsacct;
    -- V$PDBS privileges
    grant select on V_$PDBS to rdsdt_dtsacct;
    grant select on v$database to rdsdt_dtsacct;
    grant select on dba_objects to rdsdt_dtsacct;
    grant select on DBA_TAB_COMMENTS to rdsdt_dtsacct;
    grant select on dba_tab_cols to rdsdt_dtsacct;
    grant select_catalog_role TO rdsdt_dtsacct;
    
    # Switch to the CDB$ROOT, which is the root container of the container database (CDB). Create a database account and grant permissions to the account.
    ALTER SESSION SET container = CDB$ROOT;
    # Create a database account named rdsdt_dtsacct and grant permissions to the account. You must modify the default parameters of the Oracle database. 
    alter session set "_ORACLE_SCRIPT"=true;
    create user rdsdt_dtsacct IDENTIFIED BY rdsdt_dtsacct;
    grant create session to rdsdt_dtsacct;
    grant connect to rdsdt_dtsacct;
    grant select on v_$logmnr_contents to rdsdt_dtsacct;
    grant LOGMINING TO rdsdt_dtsacct;
    grant EXECUTE_CATALOG_ROLE to rdsdt_dtsacct;
    grant execute on sys.dbms_logmnr to rdsdt_dtsacct;
    
    # Create a database account named rdsdt_dtsacct and grant permissions to the account.
    create user rdsdt_dtsacct IDENTIFIED BY rdsdt_dtsacct;
    grant create  session to rdsdt_dtsacct;
    grant connect  to rdsdt_dtsacct;
    grant resource to rdsdt_dtsacct;
    grant select on V_$LOGMNR_LOGS to rdsdt_dtsacct;
    grant select on  all_objects to rdsdt_dtsacct;
    grant select on  all_tab_cols to rdsdt_dtsacct;
    grant select on  dba_registry to rdsdt_dtsacct;
    grant select any table to rdsdt_dtsacct;
    grant select any transaction to rdsdt_dtsacct;
    grant select on v$database to rdsdt_dtsacct;
    grant select on dba_objects to rdsdt_dtsacct;
    grant select on DBA_TAB_COMMENTS to rdsdt_dtsacct;
    grant select on dba_tab_cols to rdsdt_dtsacct;
    -- v$log privileges
    grant select on v_$log to rdsdt_dtsacct;
    -- v$logfile privileges
    grant select on v_$logfile to rdsdt_dtsacct;
    -- v$archived_log privileges
    grant select on v_$archived_log to rdsdt_dtsacct;
    -- v$parameter privileges
    grant select on v_$parameter to rdsdt_dtsacct;
    -- v$database privileges
    grant select on v_$database to rdsdt_dtsacct;
    -- v$active_instances privileges
    grant select on v_$active_instances to rdsdt_dtsacct;
    -- v$instance privileges
    grant select on v_$instance to rdsdt_dtsacct;
    -- v$logmnr_contents privileges
    grant select on v_$logmnr_contents to rdsdt_dtsacct;
    grant select on sys.USER$ to rdsdt_dtsacct;
    grant select on SYS.OBJ$ to rdsdt_dtsacct;
    grant select on SYS.COL$ to rdsdt_dtsacct;
    grant select on SYS.IND$ to rdsdt_dtsacct;
    grant select on SYS.ICOL$ to rdsdt_dtsacct;
    grant select on SYS.CDEF$ to rdsdt_dtsacct;
    grant select on SYS.CCOL$ to rdsdt_dtsacct;
    grant select on SYS.TABPART$ to rdsdt_dtsacct;
    grant select on SYS.TABSUBPART$ to rdsdt_dtsacct;
    grant select on SYS.TABCOMPART$ to rdsdt_dtsacct;
    grant LOGMINING TO rdsdt_dtsacct;
    grant EXECUTE_CATALOG_ROLE to rdsdt_dtsacct;
    grant execute on sys.dbms_logmnr to rdsdt_dtsacct;
    grant select_catalog_role TO rdsdt_dtsacct;

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
  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 page that appears, configure the source and destination databases.

    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.

    Category

    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

    Database Type

    The type of the source database. Select Oracle.

    Access Method

    The access method of the source database. In this example, Public IP Address is selected.

    Note

    If you select other access methods, you must set up the environment that is required for the self-managed Oracle database. For more information, see Preparation overview.

    Instance Region

    The region in which the source Oracle database resides.

    Hostname or IP address

    The endpoint that is used to connect to the self-managed Oracle database.

    Port Number

    The service port number of the self-managed Oracle database. Default value: 1521.

    Note

    In this example, the service port of the self-managed Oracle database must be accessible over the Internet.

    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 Account

    The account of the source Oracle database. For more information about the permissions that are required for the account, see the Preparations section of this topic.

    Database Password

    The password of the database account.

    Destination Database

    Database Type

    The type of the destination database. Select PolarDB (Compatible with Oracle).

    Access Method

    The access method of the source database. Select Public IP Address.

    Instance Region

    Select the region where your destination PolarDB for PostgreSQL (compatible with Oracle) cluster is deployed.

    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 specify 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. Separate multiple IP:Port with commas (,).

    Database Name

    The name of the destination database in the PolarDB for PostgreSQL (compatible with Oracle) cluster.

    Database Account

    The database account of the destination PolarDB for PostgreSQL (compatible with Oracle) cluster. For more information about the permissions that are required for the account, see Before you begin.

    Database Password

    The password of the database account.

  4. If an IP address whitelist is configured for your self-managed database, add the CIDR blocks of DTS servers to the IP address whitelist. Then, click Test Connectivity and Proceed.

    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. Select objects to be migrated for the task and configure advanced settings.

    • Basic Settings

      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 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.

      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.

      Rename Databases and Tables

      • 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 the "Map the name of a single object" section of the Map object names topic.

      • To rename multiple objects at a time, click Batch Edit in the upper-right corner of the Selected Objects section. For more information, see the "Map multiple object names at a time" section of the Map object names topic.

      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.

      Filter the data to be migrated

      You can specify WHERE conditions to filter data. For more information, see Set filter conditions.

      Select SQL operations for incremental data migration

      In the Selected Objects section, right-click an object to be migrated. In the dialog box that appears, 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.

    • Advanced Settings

      Parameter

      Description

      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.

  6. 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 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.

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

  8. 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

    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.

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

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