Migrate self-managed Oracle to Message Queue for Apache Kafka

Usage notes

• A full data migration consumes read and write resources on both the source and destination databases, increasing their server load. This added load can degrade performance or cause service unavailability, especially if your databases have poor performance, low specifications, or are already busy (for example, with many slow SQL queries, tables without primary keys, or deadlocks in the destination database). Before you start the migration, evaluate the performance of both databases and perform the migration during off-peak hours, for example, when CPU utilization is below 30%.

• If a migration task fails, DTS automatically tries to resume it. Before you switch your business to the destination database, you must stop or release the task. This prevents the resumed task from overwriting data in the destination database with data from the source.

• 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 a data center to DTS through VPN Gateway.

  Important

  When you configure the source Oracle database in the DTS console, you can specify the SCAN IP address of the Oracle RAC as the database endpoint or IP address.

• If your self-managed Oracle database is version 12c or later, the names of tables to be migrated cannot exceed 30 bytes in length.

• If a source table to be migrated lacks a primary key or unique constraint, duplicate data may occur in the destination database.

Billing

Migration types

Before you begin

Log on to the Oracle database that you want to migrate, create a database account for data collection, and grant the necessary permissions to the account.

To create a database account and grant permissions:

For a self-managed Oracle database, see CREATE USER and GRANT.

Enable logging and grant fine-grained permissions to an Oracle database 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 Execute the following statement to enable minimal supplemental logging: alter database add supplemental log data; 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 Execute the following statement to enable minimal supplemental logging: alter database add supplemental log data; 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 statements to enable force logging: alter database force logging;

2. Grant fine-grained permissions to an Oracle database account.

   Oracle versions 9i to 11g

   # 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;

   Oracle 12c to 19c (multitenant)

   # 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;

   Oracle 12c to 19c (non-multitenant)

   # 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;

   Note

   For more information about the multitenant architecture of Oracle, see Oracle Multitenant.

Procedure

1. Log on to the DTS console.

   Note

   If you are automatically redirected to the Data Management (DMS) console, you can click the icon in the lower-right corner and then click to return to the classic DTS console.

2. In the left-side navigation pane, click Data Migration.

3. At the top of the Migration Tasks page, select the destination instance's region.

4. In the upper-right corner of the page, click Create Data Migration Task.

5. Configure the connection settings for the source and destination databases.

   Category	Parameter	Description
   N/A	Task Name	DTS automatically generates a task name. We recommend that you specify a descriptive name for easy identification. The name does not need to be unique.
   Source database	Instance type	Select how the source database is deployed. This topic uses User-Created Database with Public IP Address as an example. Note If you use a different instance type for your self-managed database, you must perform additional preparations. For more information, see Preparation overview.
   	Instance region	If you select User-Created Database with Public IP Address as the instance type, you do not need to set the Instance Region. Note If you have configured a whitelist for your self-managed Oracle database, click Get IP Address Segment of DTS next to the Instance Region setting to obtain the IP addresses of the DTS servers. Then, add these IP addresses to the security whitelist of your self-managed Oracle database.
   	Database type	Select Oracle.
   	Hostname or IP address	Enter the endpoint of the self-managed Oracle database. In this case, enter its public IP address.
   	Port number	Enter the service port of the self-managed Oracle database. The default value is 1521. Note In this example, the service port is accessible over the internet.
   	Instance type	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 account for the self-managed Oracle database. For information about the required permissions, see Before you begin.
   	Database password	Enter the password for the database account. Note After you configure the source database, click Test Connectivity next to Database Password to verify that the connection information is correct. If the connection information is valid, a Passed message appears. If a Failed message appears, click Diagnose next to Failed and modify the settings as prompted.
   Destination database	Instance type	Select User-Created Database Connected Over Express Connect, VPN Gateway, or Smart Access Gateway. Note Because DTS does not support selecting Message Queue for Apache Kafka directly, you must configure it as a self-managed Kafka cluster.
   	Instance region	Select the region where the destination Kafka instance is located.
   	Peer VPC	Select the ID of the destination Kafka instance's VPC. You can find the VPC ID on the Basic Information page of the Kafka instance.
   	Database type	Select Kafka.
   	IP address	Enter any IP address from the Default Endpoint of the Kafka instance. Note You can find the IP address of the Default Endpoint on the Basic Information page of the Kafka instance.
   	Port number	The service port of the Kafka instance. The default value is 9092.
   	Database account	Enter the username for the Kafka instance. Note If the instance type of the Kafka instance is VPC Instance, you do not need to configure Database Account and Database Password.
   	Database password	Enter the password for the username.
   	Topic	Click Get Topic list on the right and select a topic from the drop-down list.
   	Topic for storing DDL	Click Get Topic list on the right and select a topic from the drop-down list to store DDL information. If you do not specify a topic, DTS stores the DDL information in the topic selected for the Topic setting.
   	Kafka version	Select the version that corresponds to your Kafka instance.
   	Connection method	Based on your business and security requirements, select Non-encrypted or SCRAM-SHA-256.
   	Use Kafka schema registry	Kafka Schema Registry is a metadata service layer that provides a RESTful interface for storing and retrieving Avro schemas. No: Does not use Kafka Schema Registry. Yes: Uses Kafka Schema Registry. You must enter the URL or IP address of the Avro schema registered in Kafka Schema Registry.

6. After you complete the configurations, click Set Whitelist and Next in the lower-right corner of the page.
   If the source or destination is an Alibaba Cloud database instance (such as ApsaraDB RDS for MySQL or ApsaraDB for MongoDB), DTS automatically adds the IP addresses of the DTS servers in the corresponding region to the instance's whitelist. If the source or destination is a self-managed database on an ECS instance, DTS automatically adds the IP addresses of the DTS servers to the ECS instance's security group rules. You must also ensure that the self-managed database allows access from the ECS instance. If your database is a cluster deployed across multiple ECS instances, you must manually add the regional IP addresses of the DTS servers to the security group rules of each ECS instance. If the source or destination is a self-managed database in an on-premises data center or a third-party cloud database, you must manually add the IP addresses of the DTS servers to allow access. For a list of DTS server IP addresses, see CIDR blocks of DTS servers.

   Warning

   Adding public IP addresses of DTS servers, whether automatically or manually, may introduce security risks. By using this product, you acknowledge and accept these potential risks. You are responsible for implementing basic security measures, such as using strong passwords, restricting open ports, using authentication for internal APIs, regularly reviewing and limiting unnecessary network segments, or connecting by using private connections such as Express Connect, VPN Gateway, or Smart Access Gateway.

7. Configure the migration types, policy, and objects.

   Parameter	Description
   Migration type	Select Schema Migration, Full Data Migration, and Incremental Data Migration. Important If you do not select Incremental Data Migration, do not write new data to the source database during the full data migration to ensure data consistency.
   Data format in Kafka	Data migrated to the Kafka cluster is stored in Avro format. You must parse the data based on the Avro schema definition. For more information, see DTS Avro schema definition.
   Policy for migrating data to Kafka partitions	Select a migration policy based on your business requirements. For more information, see Kafka partition migration policies.
   Migration objects	In the Available box, click the tables you want to migrate, and then click the icon to move them to the Selected Objects box. Note DTS automatically maps the table names to the topic name you selected in Step 5. To change the destination topic for a migration, see Map tables and columns.
   Rename objects	To change the name of an object in the destination instance, use the object name mapping feature. For more information, see Map tables and columns.
   Connection retry duration	By default, DTS retries for 12 hours. You can also specify a custom retry duration. If DTS reconnects to the source or destination database within the specified time, the migration task automatically resumes. Otherwise, the task fails. Note DTS charges fees for the task while it retries to connect. We recommend that you set a custom retry duration based on your business needs or release the DTS instance as soon as possible after the source and destination database instances are released.

8. In the lower-right corner, click Precheck and Start.

   Important

   • DTS runs a precheck before starting the migration task. The task can start only after this precheck passes.

   • If the precheck fails, click the icon next to the failed item to view its details.

     • You can fix the issues based on the details and then run the precheck again.

     • If you do not need to fix the warning items, you can select Ignore or Ignore Warning Items and Run Precheck Again to skip the warning items and run the precheck again.

9. After the task passes the precheck, click Next.

10. In the Confirm Settings dialog box that appears, select a Instance Class and select the Data Transmission Service (pay-as-you-go) Service Terms checkbox.

11. Click Buy and Start to start the migration task.

Stop the data migration task

• Full data migration

  Do not manually stop a task during full data migration. Otherwise, the system may fail to migrate all data. Wait until the migration task automatically ends.

• Incremental data migration

  The task does not stop automatically. You must stop it manually.

  1. Wait until the task stage changes to Incremental Data Migration and the status shows Undelayed. Then, stop writing data to the source database for a few minutes. The Incremental Data Migration status may temporarily show a delay.
  2. When the Incremental Data Migration status returns to Undelayed, manually stop the migration task.