This topic describes how to migrate data from a self-managed Oracle database to an AnalyticDB for PostgreSQL instance by using Data Transmission Service (DTS). After you migrate data, you can build real-time data warehouses in the destination instance.
Prerequisites
- The source Oracle database and the destination AnalyticDB for PostgreSQL instance are created.
Note
- For more information about how to create the destination AnalyticDB for PostgreSQL instance, see Create an AnalyticDB for PostgreSQL instance.
- 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.
Limits
Category | Description |
---|---|
Limits on the source database |
|
Other limits |
|
Billing
Migration type | Task configuration fee | Internet traffic fee |
---|---|---|
Schema migration and 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 |
---|---|
Schema migration | DTS migrates the schemas of the required objects from the source database to the destination
AnalyticDB for PostgreSQL instance. DTS supports schema migration for the following types of objects: table,
index, constraint, function, sequence, and view.
Warning
|
Full data migration | DTS migrates historical data of the required objects from the source database to the destination AnalyticDB for PostgreSQL instance. |
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 AnalyticDB for PostgreSQL instance in real time.
Incremental data migration ensures service continuity of self-managed applications during data migration. |
SQL operations that can be migrated
Operation type | SQL statement |
---|---|
DML | INSERT, UPDATE, and DELETE |
DDL | ADD COLUMN |
Data type mappings
For more information about, see Data type mappings between heterogeneous databases.
Preparations
Log on to the source Oracle database, create an account for data collection, and grant permissions to the account.
Database | Schema migration | Full data migration | Incremental data migration |
---|---|---|---|
Self-managed Oracle database | Permissions of the schema owner | Permissions of the schema owner | Database administrator (DBA) |
AnalyticDB for PostgreSQL instance | Write permissions on the destination database |
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.