tencent cloud

Data Transfer Service

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Data Migration
Data Sync
Data Subscription (Kafka Edition)
Strengths
Supported Regions
Specification Description
Purchase Guide
Billing Overview
Configuration Change Description
Payment Overdue
Refund
Getting Started
Data Migration Guide
Data Sync Guide
Data Subscription Guide (Kafka Edition)
Preparations
Business Evaluation
Network Preparation
Adding DTS IP Addresses to the Allowlist of the Corresponding Databases
DTS Service Permission Preparation
Database and Permission Preparation
Configuring Binlog in Self-Built MySQL
Data Migration
Databases Supported by Data Migration
Cross-Account TencentDB Instance Migration
Migration to MySQL Series
Migrating to PostgreSQL
Migrating to MongoDB
Migrating to SQL Server
Migrating to Tencent Cloud Distributed Cache
Task Management
Data Sync
Databases Supported by Data Sync
Cross-Account TencentDB Instance Sync
Sync to MySQL series
Synchronize to PostgreSQL
Synchronization to MongoDB
Synchronize to Kafka
Task Management
Data Subscription (Kafka Edition)
Databases Supported by Data Subscription
MySQL series Data Subscription
Data Subscription for TDSQL PostgreSQL
MongoDB Data Subscription
Task Management
Consumption Management
Fix for Verification Failure
Check Item Overview
Cutover Description
Monitoring and Alarms
Supported Monitoring Indicators
Supported Events
Configuring Metric Alarms and Event Alarms via the Console
Configuring Indicator Monitoring and Event Alarm by APIs
Ops Management
Configuring Maintenance Time
Task Status Change Description
Practical Tutorial
Synchronizing Local Database to the Cloud
Creating Two-Way Sync Data Structure
Creating Many-to-One Sync Data Structure
Creating Multi-Site Active-Active IDC Architecture
Selecting Data Sync Conflict Resolution Policy
Using CLB as Proxy for Cross-Account Database Migration
Migrating Self-Built Databases to Tencent Cloud Databases via CCN
Best Practices for DTS Performance Tuning
FAQs
Data Migration
Data Sync
FAQs for Data Subscription Kafka Edition
Regular Expressions for Subscription
Error Handling
Common Errors
Failed Connectivity Test
Failed or Alarmed Check Item
Inability to Select Subnet During CCN Access
Slow or Stuck Migration
Data Sync Delay
High Data Subscription Delay
Data Consumption Exception
API Documentation
History
Introduction
API Category
Making API Requests
(NewDTS) Data Migration APIs
Data Sync APIs
Data Consistency Check APIs
(NewDTS) Data Subscription APIs
Data Types
Error Codes
DTS API 2018-03-30
Service Agreement
Service Level Agreements
DocumentationData Transfer Service

Target Database Content Conflict Check

Focus Mode
Font Size
Last updated: 2022-09-21 18:04:04

Check Details

MySQL/MariaDB/Percona/TDSQL-C for MySQL/TDSQL for MySQL check requirements

The target instance cannot have objects with the same name as those in the source database. If a conflict causes an error, you can fix it in one of the following methods:
During entire instance migration, the target instance must be empty. If a conflict causes an error, you need to delete the instance content.
If advanced objects are selected, the target database cannot have conflicting advanced objects. If a conflict causes an error, you need to delete the conflicting objects.

PostgreSQL check requirements

The target instance cannot have objects with the same name as those in the source database.
During entire instance migration, the target instance must be empty. If a conflict causes an error, you need to delete the instance content.

MongoDB check requirements

The target instance can have tables with the same name as those in the source database, but they must be empty tables. If a conflict causes an error, you can fix it in one of the following methods:
Option 1: Delete tables with the same name in the target database or clear their data.

SQL Server check requirements

The target instance cannot have databases with the same name as those in the source database; otherwise, an error will be reported.
If an error is reported, you need to delete or rename databases with the same name from the target database.

Redis check requirements

The target instance must be empty; otherwise, an error will be reported.
If an error is reported, delete the content in the target instance and restart the verification task.

Troubleshooting

Using table mapping (for MySQL/MariaDB/Percona/TDSQL-C for MySQL/TDSQL for MySQL only)

You can use the DTS table mapping feature to map the names of the objects to be migrated with the same name to other names in the target database.
1. Log in to the DTS console, select the corresponding migration task, and click More > Modify in the Operation column.
2. In Selected Object on the right, hover over an object to be modified, click the displayed Edit icon, and rename the object.

3. Run the verification task again.

Modifying objects with the same name in target database

Log in to the target database, rename or delete the objects with the same name as the migration objects.

Removing objects with the same name from migration objects

Modify the migration task configuration to remove the objects with the same name from the migration objects. The removed objects cannot be migrated.
1. Log in to the DTS console, select the corresponding migration task, and click More > Modify in the Operation column.
2. Remove the objects with the same name from the migration objects.
3. Run the verification task again.

Deleting the target database content

Log in to the target database, delete the objects with the same name as those in the source database or the entire database, and run the verification task again.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback