Migrate data from a self-managed Oracle database to an AnalyticDB for PostgreSQL instance

Limits

Billing

Migration types

SQL operations that can be migrated

Before you begin

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

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

• Self-managed Oracle database: CREATE USER and GRANT

• The initial account of the destination AnalyticDB for PostgreSQL instance has the required permissions. For more information, see Create a database account.
  Note You can also enter an account that has the RDS_SUPERUSER permission. For more information, see Manage users and permissions.

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 Enable minimal supplemental logging: alter database add supplemental log data; 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 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 Oracle Versions 12c to 19c (Multitenant Architecture) Oracle Versions 12c to 19c (Non-Multitenant Architecture)

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

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

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

   Note To create a global account starting with C## for a multitenant CDB$ROOT 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, click DTS.
2. In the upper-left corner of the page, select the region in which the data migration instance resides.
   
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.

   

   Section	Parameter	Description
   N/A	Task Name	DTS automatically generates a task name. We recommend that you specify a descriptive name that makes it easy to identify. You do not need to use a unique task name.
   Source Database	Database Type	Select Oracle.
   	Access Method	Select an access method based on the deployment of the source database. In this example, select Public IP Address. Note If you select other types of self-managed databases, you must deploy the network environment for the source database. For more information, see Preparation overview.
   	Instance Region	Select the region where the source Oracle database resides.
   	Hostname or IP Address	Enter the endpoint that is used to connect to the self-managed Oracle database.
   	Port Number	Enter the service port number of the self-managed Oracle database. The default port number is 1521. Note The service port of the self-managed Oracle database must be accessible over the Internet.
   	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.
   Destination Database	Database Type	Select AnalyticDB for PostgreSQL.
   	Access Method	Select Alibaba Cloud Instance.
   	Instance Region	Select the region where the destination AnalyticDB for PostgreSQL instance resides.
   	Instance ID	Select the ID of the destination AnalyticDB for PostgreSQL instance.
   	Database Name	Enter the name of the destination database in the AnalyticDB for PostgreSQL instance.
   	Database Account	Enter the database account of the destination AnalyticDB for PostgreSQL instance. For information about the permissions that are required for the account, see Before you begin.
   	Database Password	Enter the password of the database account.

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

   • If the source or destination database instance is an Alibaba Cloud database instance, such as an ApsaraDB RDS for MySQL or ApsaraDB for MongoDB instance, or is a self-managed database hosted on Elastic Compute Service (ECS), DTS automatically adds the CIDR blocks of DTS servers to the whitelist of the database instance or ECS security group rules. For more information, see Add the CIDR blocks of DTS servers to the security settings of on-premises databases. If the source or destination database is a self-managed database on data centers or is from other cloud service providers, you must manually add the CIDR blocks of DTS servers to allow DTS to access the database.
   • If the CIDR blocks of DTS servers are automatically or manually added to the whitelist of the database instance or ECS security group rules, 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: enhance the security of your account and password, limit the ports that are exposed, authenticate API calls, regularly check the whitelist or ECS security group rules and forbid unauthorized CIDR blocks, or connect the database to DTS by using Express Connect, VPN Gateway, or Smart Access Gateway.
   • After the DTS task is completed or released, we recommend that you manually detect and remove the added CIDR blocks from the whitelist of the database instance or ECS security group rules.
5. Configure objects to migrate and advanced settings.
   • Basic 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 inconsistency may occur 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 specific columns are migrated or the data migration task fails.
     Select 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 Map the name of a single object. To rename multiple objects at a time, click 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 DDL and DML operations that you want to migrate. For more information, see SQL operations that can be migrated.

   • Advanced 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.
     Retry Time for Failed Connections	Specify the retry time range for failed connections. Valid values: 10 to 720. Unit: minutes. Default value: 720. We recommend that you set the retry time range to more than 30 minutes. If DTS reconnects to the source and destination databases within the specified time range, DTS resumes the data synchronization task. Otherwise, the data synchronization task fails. Note If an instance serves as the source or destination database of multiple data synchronization tasks, the value that is set 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 needs. You can also release the DTS instance at your earliest opportunity after the source and destination instances are released.

6. Specify the primary key columns and distribution keys of the tables that you want to migrate to the AnalyticDB for PostgreSQL instance.
   
7. 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, you can click the icon next to each failed item to view details.
     • You can troubleshoot the issues based on the causes and run a precheck again.
     • If you do not need to troubleshoot the issues, you can ignore failed items and run a precheck again.
8. Wait until the Success Rate becomes 100%. Then, click Next: Purchase Instance.
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.