Migrate an RDS for MySQL instance to a self-managed Oracle database - Data Transmission Service

This topic describes how to use Data Transmission Service (DTS) to migrate data from an RDS for MySQL instance to a self-managed Oracle database.

Prerequisites

You have created a destination self-managed Oracle database.
Note
The available storage space of the destination self-managed Oracle database must be larger than the amount of data to be migrated from the source RDS for MySQL instance.
If your self-managed Oracle database uses a Real Application Clusters (RAC) architecture, you must connect it to Alibaba Cloud through a VPC. To ensure that the DTS task runs successfully, connect the SCAN IP address and the virtual IP address (VIP) of each node in the Oracle RAC to the Alibaba Cloud VPC and configure the routes. For more information, see Overview of connection solutions for on-premises data centers and Connect an on-premises data center to DTS through a VPN Gateway.

Notes

Note

During full migration and incremental migration:

Cascade update and delete operations in the source database may cause data inconsistency.
If the destination database has foreign keys or triggers, disable them. Otherwise, the migration task may fail.

Type	Description
Source database limitations	The tables to be migrated must have primary keys or UNIQUE constraints, and the fields must be unique. Otherwise, duplicate data may appear in the destination database. If you migrate data at the table level and need to edit objects, such as mapping table or column names, a single migration task supports up to 1,000 tables. If you exceed this limit, an error is reported after you submit the task. In this case, split the tables into multiple migration tasks or configure a task to migrate the entire database. If you want to migrate incremental data, the following requirements for binary logs must be met: The binary logging feature is enabled. The binlog_format parameter is set to row and the binlog_row_image parameter is set to full. Otherwise, error messages are returned during the precheck and the data migration task fails to be started. Important If the source database is a self-managed MySQL database deployed in a dual-primary cluster, you must set the log_slave_updates parameter to ON. This ensures that DTS can obtain all binary logs. The binary logs of an ApsaraDB RDS for MySQL instance must be stored for at least three days. We recommend that you store the binary logs seven days. The binary logs of a self-managed MySQL database must be stored for at least seven days. Otherwise, DTS may fail to obtain the binary logs and the task may fail. In exceptional circumstances, data inconsistency or loss may occur. Make sure that you configure the retention period of binary logs based on the preceding requirements. Otherwise, the service reliability or performance stated in the Service Level Agreement (SLA) of DTS may not be guaranteed. Note For more information about how to set Retention Period of the binary logs of an ApsaraDB RDS for MySQL instance, see Configure parameters based on which the system automatically deletes the binary log files of an RDS instance. During schema migration and full migration, do not perform DDL operations to change the database or table schema. Otherwise, the data migration task fails. Note During full migration, DTS queries the source database. This creates metadata locks, which may block DDL operations on the source database. If you perform only full data migration, do not write new data to the source database. Otherwise, the source and destination data will be inconsistent. To maintain real-time data consistency, select Schema Migration, Full Data Migration, and Incremental Data Migration. In incremental data migration, an ApsaraDB RDS for MySQL instance that does not record transaction logs, such as a read-only ApsaraDB RDS for MySQL V5.6 instance, cannot be used as the source database. The data generated by change operation of binary logs, such as data restored from a physical backup or data from a cascade operation, is not recorded and migrated to the destination database when the data migration instance is running. Note If the change data is not recorded and migrated to the destination database, you can migrate full data again on the premise that your business is not affected. If the source database is MySQL database 8.0.23 or later, and the data to be migrated includes invisible columns, the data of the columns cannot be obtained and data loss occurs. Note To make the columns visible, run the `ALTER TABLE <table_name> ALTER COLUMN <column_name> SET VISIBLE;` command. For more information, see Invisible Columns. Tables that do not have primary keys automatically generate invisible primary keys. You need to make the invisible primary keys visible. For more information, see Generated Invisible Primary Keys.
Other limitations	Do not use tools such as pt-online-schema-change to perform online DDL operations on the migration objects in the source database. Otherwise, the migration fails. If online DDL operations that use temporary tables, including but not limited to multi-table merge scenarios, are performed on the source database, data may be lost in the destination database or the migration instance may fail. For columns of the FLOAT or DOUBLE data type, DTS reads the values using `ROUND(COLUMN,PRECISION)`. If you do not specify the precision, DTS uses a default precision of 38 for FLOAT columns and 308 for DOUBLE columns. Confirm that this precision meets your business requirements. Before data migration, evaluate the performance of the source and destination databases. We recommend that you migrate data during off-peak hours. This is because full data migration consumes read and write resources on both the source and destination databases, which may increase the database load. Full data migration runs concurrent INSERT operations. This causes table fragmentation in the destination database. As a result, the storage space used by the tables in the destination database is larger than that in the source instance. DTS attempts to resume failed migration tasks within seven days. Before you switch your business to the destination instance, make sure to stop or release the DTS instance. You can also run the `REVOKE` command to revoke the write permissions of the account that DTS uses to access the destination instance. This prevents the task from being automatically resumed, which would cause data from the source to overwrite data in the destination instance. If the source database is an ApsaraDB RDS for MySQL instance for which the EncDB feature is enabled, full data migration cannot be performed. Note ApsaraDB RDS for MySQL instances that have the Transparent Data Encryption (TDE) feature enabled support schema migration, full data migration, and incremental data migration. If an instance fails, DTS helpdesk will try to recover the instance within 8 hours. During the recovery process, operations such as restarting the instance and adjusting parameters may be performed. Note When parameters are adjusted, only the parameters of the DTS instance are modified. The parameters of the database are not modified. The parameters that may be modified include but are not limited to those described in Modify instance parameters.
Special cases	If the source database is a self-managed MySQL database, take note of the following limits: If you perform a primary/secondary switchover on the source database when the data migration task is running, the task fails. DTS calculates migration latency based on the timestamp of the latest migrated data in the destination database and the current timestamp in the source database. If no DML operation is performed on the source database for a long time, the migration latency may be inaccurate. If the latency of the data migration task is excessively high, you can perform a DML operation on the source database to update the latency. Note If you select an entire database as the object to be migrated, you can create a heartbeat table. The heartbeat table is updated or receives data every second. DTS executes the CREATE DATABASE IF NOT EXISTS `test` statement in the source database as scheduled to move forward the binary log file position. If the source database is an Apsara RDS for MySQL instance, take note of the following limit: In incremental data migration, an ApsaraDB RDS for MySQL instance that does not record transaction logs, such as a read-only ApsaraDB RDS for MySQL V5.6 instance, cannot be used as the source database. DTS executes the CREATE DATABASE IF NOT EXISTS `test` statement in the source database as scheduled to move forward the binary log file position.

Billing

Migration type	Instance configuration fee	Internet traffic fee
Schema migration and full data migration	Free of charge.	When the Access Method parameter of the destination database is set to Public IP Address, you are charged for Internet traffic. For more information, see Billing overview.
Incremental data migration	Charged. For more information, see Billing overview.

Migration types

Schema migration
DTS migrates the schema definitions of the migration objects from the source database to the destination database.
Full migration
DTS migrates all historical data of the migration objects from the source database to the destination database.
Incremental migration
After full migration, DTS migrates incremental data updates from the source database to the destination database. Incremental data migration lets you migrate data smoothly without stopping your applications.

SQL operations supported for incremental migration

Operation type	SQL statement
DML	INSERT, UPDATE, DELETE
DDL	CREATE TABLE, ALTER TABLE, RENAME TABLE, TRUNCATE TABLE, DROP TABLE

Database account permissions

Database	Schema migration	Full migration	Incremental migration
RDS for MySQL	SELECT permission	SELECT permission	REPLICATION SLAVE, REPLICATION CLIENT, and SELECT permissions on the objects to be migrated. DTS automatically grants these permissions.
Oracle	Owner permission on the schema.

To create a database account and grant permissions:

For an RDS for MySQL instance, see Create an account and Modify the permissions of an account.
For a self-managed Oracle instance, see CREATE USER and GRANT.

Procedure

This topic uses a self-managed Oracle database on an ECS instance as the destination database.

Use one of the following methods to go to the Data Migration page and select the region in which the data migration instance resides.
DTS console
1. Log on to the DTS console.
2. In the left-side navigation pane, click Data Migration.
3. In the upper-left corner of the page, select the region in which the data migration instance resides.
DMS console
Note
The actual operation 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.
1. Log on to the DMS console.
2. In the top navigation bar, move the pointer over Data + AI > DTS (DTS) > Data Migration.
3. From the drop-down list to the right of Data Migration Tasks, select the region in which the data synchronization instance resides.
Click Create Task to go to the task configuration page.

Configure the source and destination databases. The following table describes the parameters.

Category	Configuration	Description
None	Task Name	The name of the DTS task. DTS automatically generates a task name. We recommend that you specify an informative name that makes it easy to identify the task. You do not need to specify a unique task name.
Source Database	Select a DMS database instance	The database that you want to use. You can choose whether to use an existing database based on your business requirements. If you select an existing database, DTS automatically populates the parameters for the database. If you do not select an existing database, you must configure the following database information.
	Database Type	Select MySQL.
	Access Method	Select Cloud Instance.
	Instance Region	Select the region of the source RDS for MySQL instance.
	Replicate Data Across Alibaba Cloud Accounts	This example shows how to migrate data within the same Alibaba Cloud account. Select No.
	RDS Instance ID	Select the ID of the source RDS for MySQL instance.
	Database Account	Enter the database account of the source RDS for MySQL instance. For information about the required permissions, see Database account permissions.
	Database Password	The password that is used to access the database instance.
	Encryption	Specifies whether to encrypt the connection to the source database instance. Select Non-encrypted or SSL-encrypted based on your business requirements. If you want to set this parameter to SSL-encrypted, you must enable SSL encryption for the ApsaraDB RDS for MySQL instance before you configure the DTS task. For more information, see Use a cloud certificate to enable SSL encryption.
Destination Database	Select a DMS database instance	The database that you want to use. You can choose whether to use an existing database based on your business requirements. If you select an existing database, DTS automatically populates the parameters for the database. If you do not select an existing database, you must configure the following database information.
	Database Type	Select Oracle.
	Access Method	Select Self-managed Database On ECS. Note If the destination instance is a self-managed database, you must also make preparations. For more information, see Overview of preparations.
	Instance Region	Select the region of the destination self-managed Oracle instance.
	ECS Instance ID	Select the ID of the ECS instance that hosts the destination self-managed Oracle database.
	Port	Enter the service port of the destination self-managed Oracle database. The default port is 1521.
	Oracle Type	In this example, RAC Or PDB Instance is selected. Non-RAC Instance: If you select this option, you must also specify the SID. RAC Or PDB Instance: If you select this option, you must also specify the Service Name.
	Database Account	Enter the database account of the destination self-managed Oracle instance.
	Database Password	The password that is used to access the database instance.

In the lower part of the page, click Test Connectivity and Proceed, and then click Test Connectivity in the CIDR Blocks of DTS Servers dialog box that appears.
Note
Make sure that the CIDR blocks of DTS servers can be automatically or manually added to the security settings of the source and destination databases to allow access from DTS servers. For more information, see Add DTS server IP addresses to a whitelist.

Configure the objects to be migrated.

On the Configure Objects page, configure the objects that you want to migrate.

Configuration	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 Schema Migration, make sure a database and a table are created in the destination database to receive data and the object name mapping feature is enabled in Selected Objects. 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 Error: Checks whether a table with the same name exists in the destination database. If a table with the same name exists, an error is reported during the precheck and the data migration task does not start. Otherwise, the precheck is passed. Note If it is inconvenient to delete or rename the table with the same name in the destination database, you can change the table name in the destination database. For more information, see Map table and column names. Ignore Error And Continue: Skips the check for tables with the same name in the destination database. Warning Selecting Ignore Error And Continue may cause data inconsistency and business risks. For example: If the table schemas are consistent and a record in the destination database has the same primary key value as a record in the source database: During full migration, DTS retains the record in the destination database. The record from the source database is not migrated. During incremental migration, DTS does not retain the record in the destination database. The record from the source database overwrites the record in the destination database. If the table schemas are inconsistent, data initialization may fail, some data may not be migrated, or the entire migration may fail.
Capitalization of Object Names in Destination Instance	You can configure the case-sensitivity policy for the names of migrated databases, tables, and columns in the destination instance. By default, DTS Default Policy is selected. You can also choose to keep the policy consistent with the default policy of the source or destination database. For more information, see Case-sensitivity of object names in the destination database.
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	Right-click a database in the Selected Objects box. In the Edit Schema page, change the Schema Name to the schema of the destination database in the self-managed Oracle database. By default, the schema name is the same as the Database Account. For more information about the object name mapping feature, see Map table and column names. Note If you use the object name mapping feature, the migration of other objects that depend on the mapped object may fail. To set a WHERE clause to filter data, right-click the table to be migrated in the Selected Objects box and set the filter condition in the dialog box that appears. For more information, see Set filter conditions. To select SQL operations to migrate at the database or table level, right-click the migration object in the Selected Objects box and select the desired SQL operations in the dialog box that appears.

Click Next: Advanced Settings to configure advanced settings.

Configuration	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 1,440. 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 data migration 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	You can select an environment tag to identify the migration instance. In this example, no tag is required.
Whether to delete SQL operations on heartbeat tables of forward and reverse tasks	Specifies whether to write SQL operations on heartbeat tables to the source database while the DTS instance is running. Valid values: Yes: does not write SQL operations on heartbeat tables. In this case, a latency of the DTS instance may be displayed. No: writes SQL operations on heartbeat tables. In this case, features such as physical backup and cloning of the source database may be affected.
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 the Configure monitoring and alerting when you create a DTS task section of the Configure monitoring and alerting topic.

Click Next Step: Data Verification to configure the data verification task.
For more information about how to use the data verification feature, see Configure a data verification task.

Save the task settings and run a precheck.
- To view the parameters to be specified when you call the relevant API operation to configure the DTS task, move the pointer over Next: Save Task Settings and Precheck and click Preview OpenAPI parameters.
- If you do not need to view or have viewed the parameters, click Next: Save Task Settings and Precheck in the lower part of the page.
Note
- Before you can start the data migration task, DTS performs a precheck. You can start the data migration task only after the task passes the precheck.
- If the task fails to pass the precheck, click View Details next to each failed item. After you 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.

Purchase the instance.

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	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 Instance classes 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 message that appears, click OK.
You can view the progress of the task on the Data Migration page.
Note
- If a data migration task cannot be used to migrate incremental data, the task automatically stops. The Completed is displayed in the Status section.
- If a data migration task can be used to migrate incremental data, the task does not automatically stop. The incremental data migration task never stops or completes. The Running is displayed in the Status section.