|Limits on the source database
- Bandwidth requirements: The server to which the source database belongs must have
sufficient egress bandwidth. Otherwise, the data migration speed is affected.
- The tables to be migrated must have PRIMARY KEY or UNIQUE constraints and all fields
must be unique. Otherwise, the destination database may contain duplicate data records.
- If you select tables as the objects to be migrated and you need to edit tables (such
as renaming tables or columns), up to 1,000 tables can be migrated in a single data
migration task. If you run a task to migrate more than 1,000 tables, a request error
occurs. In this case, we recommend that you split the tables to be migrated, configure
multiple tasks to migrate the tables, or configure a task to migrate the entire database.
- If you need to migrate incremental data, you must make sure that the following requirements
- The write-ahead logging (WAL) feature must be enabled.
If you perform only incremental data migration, the WAL logs of the source database
must be stored for more than 24 hours. If you perform both full data migration and
incremental data migration, the WAL logs of the source database must be stored for
at least seven days. After full data migration is completed, you can set the retention
period to more than 24 hours. Otherwise, DTS may fail to obtain the WAL logs and the
task may fail. In extreme cases, data may be inconsistent or lost. Make sure that
you set the retention period of WAL logs based on the preceding requirements. Otherwise,
the Service Level Agreement (SLA) of DTS does not guarantee service reliability and
- Limits on operations:
- During full data migration, do not perform DDL operations to change the schemas of
databases or tables. Otherwise, the data migration task fails.
- If you perform only full data migration, do not write data to the source database
during data migration. Otherwise, data will be inconsistent between the source and
destination databases. To ensure data consistency, we recommend that you select Full
Data Migration and Incremental Data Migration as the migration types.
- Schema migration is not supported in this scenario. Before you configure a data migration
task, you must create databases and tables in the destination instance.
- A single data migration task can migrate data from only one database. To migrate data
from multiple databases, you must create a data migration task for each database.
- During incremental data migration, if you select a schema as the object to be migrated,
take note of the following limits: If you create a table in the schema or run the
RENAME command to rename the table, you must run the
ALTER TABLE schema.table REPLICA IDENTITY FULL; command before you write data to the table.
Note Replace the
table in the preceding sample command with the actual schema name and table name.
- To ensure that the delay time of incremental data migration is accurate, DTS adds
a heartbeat table named
dts_postgres_heartbeat to the source database. The following figure shows the schema of the heartbeat table.
- Before you migrate data, evaluate the impact of data migration on the performance
of the source and destination databases. We recommend that you migrate data during
off-peak hours. During full data migration, DTS uses read and write resources of the
source and destination databases. This may increase the loads of the database servers.
- During full data migration, concurrent INSERT operations cause fragmentation in the
tables of the destination database. After full data migration is completed, the tablespace
of the destination database is larger than that of the source database.
- You must make sure that the precision settings for columns of the FLOAT or DOUBLE
data type meets your business requirements. DTS uses the
ROUND(COLUMN,PRECISION) function to retrieve values from columns of the FLOAT or DOUBLE data type. If you
do not specify a precision, DTS sets the precision for the FLOAT data type to 38 digits
and the precision for the DOUBLE data type to 308 digits.
- DTS attempts to resume data migration tasks that failed within the last seven days.
Before you switch workloads to the destination instance, stop or release the data
migration task. You can also run the
revoke command to revoke the write permissions from the accounts that are used by DTS to
access the destination instance. Otherwise, the data in the source database will overwrite
the data in the destination instance after the task is resumed.
||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 an on-premises database to Alibaba Cloud and Configure a route between DTS and Express Connect, VPN Gateway, or Smart Access Gateway.
Notice When you configure the source Oracle database in the DTS console, you must enter the
SCAN IP address of the Oracle RAC in the Database Endpoint or IP Address field.