This topic describes how to migrate data from a self-managed Oracle database to a PolarDB for Oracle cluster by using Data Transmission Service (DTS).
Prerequisites
- The schema of the source Oracle database is migrated to the destination PolarDB for Oracle cluster by using Advanced Database & Application Migration (ADAM). For more information, see steps in Migrate the schema of a self-managed Oracle database to a PolarDB for Oracle cluster.
- The source Oracle database and the destination PolarDB for Oracle cluster are created.
Note
- For more information about how to create the destination PolarDB for Oracle cluster, see Create a PolarDB for Oracle cluster.
- For more information about the supported versions of the source database and the destination cluster, 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.
Limits
Category | Description |
---|---|
Limits on the source database |
|
Other limits |
|
Billing
Migration type | Task configuration fee | Internet traffic fee |
---|---|---|
Full data migration | Free of charge. | Charged only when data is migrated from Alibaba Cloud over the Internet. For more information, see Billing overview. |
Incremental data migration | Charged. For more information, see Billing overview. |
Migration types
Migration type | Description |
---|---|
Full data migration | DTS migrates the historical data of required objects from the self-managed Oracle
database to the destination PolarDB for Oracle cluster.
Note In this scenario, DTS does not support 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.
|
Incremental data migration | DTS retrieves redo log files from the self-managed Oracle database. Then, DTS migrates
incremental data from the self-managed Oracle database to the destination PolarDB for Oracle cluster.
Incremental data migration allows you to ensure service continuity when you migrate data from an Oracle database to a PolarDB for Oracle cluster. |
SQL operations that can be migrated
Operation type | SQL statement |
---|---|
DML | INSERT, UPDATE, and DELETE |
DDL |
|
Preparations
Log on to the self-managed Oracle database, create an account that you want to use to collect data, and then grant permissions to the account.
Database | Full data migration | Incremental data migration |
---|---|---|
Self-managed Oracle database | Permissions of the schema owner | Database administrator (DBA) |
PolarDB for Oracle cluster | Permissions of the schema owner |
To create a database account and grant permissions to the database account, perform the following operations:
-
Self-managed Oracle database: CREATE USER and GRANT
- PolarDB for Oracle cluster: Create an account