This topic describes how to migrate data from a self-managed Oracle database to a Message Queue for Apache Kafka instance by using Data Transmission Service (DTS).

Prerequisites

  • The source Oracle database and the destination Message Queue for Apache Kafka instance are created.
    Note For more information about the supported versions of the source database and the destination instance, see Overview of data migration scenarios.
  • The self-managed Oracle database is running in ARCHIVELOG mode. Archived log files are accessible and a suitable retention period is set for archived log files. For more information, see Managing Archived Redo Log Files.
  • Supplemental logging, including SUPPLEMENTAL_LOG_DATA_PK and SUPPLEMENTAL_LOG_DATA_UI, is enabled for the self-managed Oracle database. For more information, see Supplemental Logging.
  • The available storage space of the destination Message Queue for Apache Kafka instance is larger than the total size of the data in the self-managed Oracle database.
  • In the destination Message Queue for Apache Kafka instance, a topic is created to receive the migrated data. For more information, see Step 1: Create a topic.

Limits

Category Description
Limits on the source database
  • Bandwidth requirements: The server to which the source database belongs must have sufficient egress bandwidth. Otherwise, the data migration speed is affected.
  • If the self-managed Oracle database is deployed in a Real Application Cluster (RAC) architecture and is connected to DTS over an Alibaba Cloud virtual private cloud (VPC), you must connect the Single Client Access Name (SCAN) IP address of the Oracle RAC and the virtual IP address (VIP) of each node to the VPC and configure routes. The settings ensure that your DTS task can run as expected. For more information, see Connect an on-premises database to Alibaba Cloud and Configure a route between DTS and Express Connect, VPN Gateway, or Smart Access Gateway.
    Notice When you configure the source Oracle database in the DTS console, you must enter the SCAN IP address of the Oracle RAC in the Database Endpoint or IP Address field.
  • Requirements for the objects to be migrated:
    • 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 edit tables (such as rename 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 to be migrated, configure multiple tasks to migrate the tables, or call DTS API operations to configure tasks.
  • If you want to migrate incremental data, you must make sure that the following requirements are met:
    • The data logging feature must be enabled.
    • Data logs are retained for at least 7 days during full data migration. You can wait until full data migration is complete, and then clear the data logs generated in the source database after the DTS task is run.
      Note To ensure data security, DTS stores only 50 GB of data logs or the data logs for the last 24 hours. If the limit is exceeded, DTS automatically clears the cached logs.
      Warning If you clear the data logs of the source database during full data migration, the task may fail to migrate incremental data. For example, full data migration takes more than 24 hours due to the large data volume in the source database and abnormal writing in the destination database. In this case, if the data logs of the source database are cleared during full data migration, DTS cannot obtain the data logs generated 24 hours ago. Therefore, the data migration task may fail.
  • Limits on operations:
    • 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 will be inconsistent between the source and destination databases. To ensure data consistency, we recommend that you select Schema Migration, Full Data Migration, and Incremental Data Migration as the migration types.
Other limits
  • 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 read and write resources of the source and destination databases. This may increase the loads of 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.
  • DTS attempts to resume data migration tasks that failed within the last seven days. Before you switch workloads to the destination instance, stop or release the data migration task. You can also run the revoke command to revoke the write permissions from the accounts that are used by DTS to access the destination instance. Otherwise, the data in the source database will overwrite the data in the destination instance after the task is resumed.

Migration types

Migration type Description
Schema migration DTS migrates the schemas of the required objects from the source Oracle database to the destination Message Queue for Apache Kafka instance.
Note In this scenario, DTS is incompatible with 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 historical data of the required objects from the source Oracle database to the destination Message Queue for Apache Kafka instance.
Note During schema migration and full data migration, we recommend that you do not perform data definition language (DDL) operations on the required objects. Otherwise, the objects may fail to be migrated.
Incremental data migration DTS retrieves redo log files from the source Oracle database. Then, DTS synchronizes incremental data from the source Oracle database to the destination Message Queue for Apache Kafka instance. Incremental data migration allows you to ensure service continuity when you migrate data from a self-managed Oracle database.

SQL operations that can be migrated

Operation type SQL statements
DML INSERT, UPDATE, and DELETE
DDL
  • CREATE TABLE, ALTER TABLE, DROP TABLE, RENAME TABLE, and TRUNCATE TABLE
  • CREATE VIEW, ALTER VIEW, and DROP VIEW
  • CREATE PROCEDURE, ALTER PROCEDURE, and DROP PROCEDURE
  • CREATE FUNCTION, DROP FUNCTION, CREATE TRIGGER, and DROP TRIGGER
  • CREATE INDEX and DROP INDEX

Before you begin

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

Note If you have created a database account and the account has the permissions that are listed in the following table, skip this step.
Database Schema migration Full data migration Incremental data migration
Source Oracle database The permissions of the schema owner The permissions of the schema owner Database administrator (DBA)

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

Self-managed Oracle database: CREATE USER and GRANT

  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:
    Note You can enable database-level supplemental logging to ensure the stability of 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. Enable minimal supplemental logging:
        alter database add supplemental log data;
      2. 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. 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 ;
  2. Grant fine-grained permissions to an Oracle database account
    # Create a database account, for example, 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;
    # Switch to the pluggable database (PDB). Create a database account, for example, 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;
    
    # Switch to the container database (CDB). Create a database account and grant permissions to the account by using one of the following methods:
    ALTER SESSION SET container = CDB$ROOT;
    Method 1: Create a global account starting with C##, for example, C##rdsdt_dtsacct, and grant permissions to the account. If you use this method, you must submit a ticket and contact the DTS team to modify some parameters. The link to submit a ticket is provided in the note.
    create user C##rdsdt_dtsacct IDENTIFIED BY rdsdt_dtsacct;
    grant create session to C##rdsdt_dtsacct;
    grant connect to C##rdsdt_dtsacct;
    grant resource to C##rdsdt_dtsacct;
    grant select on v_$logmnr_contents to rdsdt_dtsacct;
    grant LOGMINING to C##rdsdt_dtsacct;
    grant EXECUTE_CATALOG_ROLE to C##rdsdt_dtsacct;
    grant execute on sys.dbms_logmnr to C##rdsdt_dtsacct;
    Method 2: Create a database account, for example, rdsdt_dtsacct, and grant permissions to the account. If you use this method, 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, for example, 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;
    -- 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;
    Note To create a global account starting with C## for a multitenant container database (CDB) in Oracle 12c to 19c, you must submit a ticket and contact the DTS team to modify some parameters.

Procedure

  1. Go to the Data Migration page of the new DTS console.
    Note You can also log on to the Data Management (DMS) console. In the top navigation bar, choose DTS > Data Migration.
  2. In the upper-left corner of the page, select the region where the data migration instance resides.
    Select a region
  3. Click Create Task. On the page that appears, configure the source and destination databases.
    Warning After you select the source and destination instances, we recommend that you read the limits displayed at the top of the page. This helps you create and run the data migration task.
    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 to identify the task. You do not need to use a unique task name.

    Source Database Select Template
    If the connection settings of the instance has been saved as a template, you can select the connection name. DTS automatically applies the saved connection settings.
    Note
    • You can modify the connection settings of a template.
    • To edit the template name, you can click Edit Template Name at the bottom of the Source Database section.
    • The modified connection template will take effect the next time you select the connection template. The database instance that you have configured by using the template is not affected.
    Database Type Select Oracle.
    Access Method Select an access method based on the deployment of the source database. In this example, select Self-managed Database on ECS.
    Note If your source database is a self-managed database, you must deploy the network environment for the database. For more information, see Preparation overview.
    Instance Region Select the region where the source Oracle database resides.
    ECS Instance ID Select the ID of the Elastic Compute Service (ECS) instance that hosts the self-managed Oracle database.
    Port Number Enter the service port number of the self-managed Oracle database. The default port number is 1521.
    Oracle Type
    • If you select Non-RAC Instance, you must specify the SID parameter.
    • If you select RAC or PDB Instance, you must specify the Service Name parameter.
    In this example, select Non-RAC Instance.
    Database Account Enter the account of the source Oracle database. For information about the permissions that are required for the account, see Before you begin.
    Database Password

    Enter the password of the database account.

    Save as Template
    Click Save as Template. In the dialog box that appears, set the name of the database connection, and click OK. The connection settings of the database instance is saved as a template.
    Note We recommend that you specify an informative name to identify the database connection. You do not need to use a unique name.
    Destination Database Select Template
    If the connection settings of the instance has been saved as a template, you can select the connection name. DTS automatically applies the saved connection settings.
    Note
    • You can modify the connection settings of a template.
    • To edit the template name, you can click Edit Template Name at the bottom of the Source Database section.
    • The modified connection template will take effect the next time you select the connection template. The database instance that you have configured by using the template is not affected.
    Database Type Select Kafka.
    Access Method Select Express Connect, VPN Gateway, or Smart Access Gateway.
    Note You cannot select Message Queue for Apache Kafka as the access method. You can use Message Queue for Apache Kafka as a self-managed Kafka database to configure data migration.
    Instance Region Select the region where the destination Message Queue for Apache Kafka instance resides.
    Connected VPC Select the ID of the virtual private cloud (VPC) to which the destination Message Queue for Apache Kafka instance belongs. To obtain the VPC ID, you can log on to the Message Queue for Apache Kafka console and go to the Instance Details page of the Message Queue for Apache Kafka instance. In the Basic Information section, you can view the VPC ID.
    Hostname or IP Address Enter an IP address that is included in the Default Endpoint parameter of the Message Queue for Apache Kafka instance.
    Note To obtain an IP address, you can log on to the Message Queue for Apache Kafka console and go to the Instance Details page of the Message Queue for Apache Kafka instance. In the Basic Information section, you can obtain an IP address from the Default Endpoint parameter.
    Port Number Enter the service port number of the Message Queue for Apache Kafka instance. The default port number is 9092.
    Database Account Enter the database account of the Message Queue for Apache Kafka instance.
    Note If the instance type of the Message Queue for Apache Kafka instance is VPC Instance, you do not need to specify the database account or database password.
    Database Password

    Enter the password of the database account.

    Kafka Version Select the version of the Message Queue for Apache Kafka instance.
    Encryption Select Non-encrypted or SCRAM-SHA-256 based on your business and security requirements.
    Topic Select a topic from the drop-down list.
    Topic That Stores DDL Information Select a topic from the drop-down list. The topic is used to store the DDL information. If you do not specify this parameter, the DDL information is stored in the topic that is specified by the Topic parameter.
    Whether to Use Kafka Schema Registry Kafka Schema Registry provides a serving layer for your metadata. It provides a RESTful interface for storing and retrieving your Avro schemas.
    • No: Kafka Schema Registry is not used.
    • Yes: Kafka Schema Registry is used. In this case, you must enter the URL or IP address that is registered in Kafka Schema Registry for your Avro schemas.
    Save as Template
    Click Save as Template. In the dialog box that appears, set the name of the database connection, and click OK. The connection settings of the database instance is saved as a template.
    Note We recommend that you specify an informative name to identify the database connection. You do not need to use a unique name.
  4. If a whitelist is configured for your self-managed database, you must add the CIDR blocks of DTS servers to the whitelist. Then, click Test Connectivity and Proceed.
  5. Select objects for the task and configure advanced settings.
    • Basic SettingsBasic Settings
      Parameter Description
      Task Stages
      • 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 Incremental Data Migration is not selected, we recommend that you do not write data to the source instance during data migration. This ensures data consistency between the source and destination instances.
      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 identical table names, the precheck is passed. Otherwise, an error is returned during 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 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 consistency is not guaranteed and your business may be exposed to potential risks.
        • If the source and destination databases have the same schema, DTS does not migrate data records that have the same primary keys as data records in the destination database.
        • If the source and destination databases have different schemas, only some columns are migrated or the data migration task fails.
      Data Format in Kafka Select the format in which data records are stored in the Message Queue for Apache Kafka instance.
      • If you select DTS Avro, data is parsed based on the schema definition of DTS Avro. For more information, see DTS Avro schema.
      • If you select SharePlex JSON, data is stored in the SharePlex JSON format. For more information, see SharePlex JSON.
      Policy for Shipping Data to Kafka Partitions Select a migration policy based on your business requirements. For more information, see Specify the policy for migrating data to Kafka partitions.
      Select Objects

      Select one or more objects from the Source Objects section and click the Rightwards arrow icon to move the objects to the Selected Objects section.

      Note You can select columns, tables, or databases 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, and stored procedures to the destination database.
      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 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.
      Filter data

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

      Select the SQL operations to be migrated In the Selected Objects section, right-click an object. In the dialog box that appears, select the DML operations that you want to migrate. For more information, see SQL operations that can be migrated.
    • Advanced SettingsAdvanced Settings
      Parameter Description
      Set Alerts
      Specify whether to set alerts for the data migration task. If the task fails or the migration latency exceeds the threshold, the alert contacts will receive notifications.
      • Select No if you do not want to set alerts.
      • Select Yes to set alerts. In this case, you must also set the alert threshold and alert contacts.
      Capitalization of Object Names in Destination Instance

      Specify 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 of the source or destination database. For more information, see Specify the capitalization of object names in the destination instance.

      Retry Time for Failed Connections
      Specify the retry time for failed connections. Valid values: 10 to 1440. Unit: minutes. Default value: 120. We recommend that you set the retry time to more than 30 minutes. 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
      • If multiple DTS instances have the same source or destination database, the lowest value takes effect. For example, the retry time is set to 30 minutes for Instance A and 60 minutes for Instance B, DTS retries failed connections at an interval of 30 minutes.
      • 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.
  6. In the lower part of the page, click Next: Save Task Settings and Precheck.
    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, you can click the Info icon 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.
  7. Wait until the Success Rate becomes 100%. Then, click Next: Purchase Instance.
  8. On the Purchase Instance page, specify the Instance Class parameter for the data migration instance. The following table describes the parameter.
    Section Parameter Description
    Parameters Instance Class

    DTS provides several instance classes that have different performance in 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 select Data Transmission Service (Pay-as-you-go) Service Terms.
  10. Click Buy and Start to start the data migration task. You can view the progress of the task in the task list.