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

Error Handling

PDF

フォーカスモード

フォントサイズ

最終更新日: 2024-09-25 11:27:15

Problem Scenario
After the migration task officially starts, it will go through the following  Migration Steps.
1. Prohibit backup Jobs.
2. Back up databases.
3. Transfer backup files.
4. Restore databases.
5. Deploy real-time synchronization (This step is involved only when the migration type is: full + incremental migration).
During the above migration steps, if a task failure occurs, click Error Message to understand the cause of the task failure, and click Error Details for handling suggestions.
Problem Handling
The following table lists the error messages of migration task failures and handling suggestions.
Serial Number
Error Message
Suggestions
1
Task failed. Please submit a ticket to get a solution.
Please  submit a ticket  to get a solution.
2
The database to be migrated was not found in the source instance.
The database to be migrated was not found in the source instance. Please confirm whether the database to be migrated exists in the source instance.
3
The migration initialization operation cannot be performed on the source instance.
The migration initialization operation cannot be performed on the source instance:
1. Please check if the SQL service startup account for the source instance is using the built-in Local System account. You need to select "Built-in account" in "Log on as" in the startup configuration and modify it to start with the Local System account.
2. Please check if the source instance has xp_cmdshell enabled. You need to enable xp_cmdshell.
3. Please ensure that the migration account has sysadmin permissions.
4
Later-version instances cannot migrate to earlier-version instances.
Later-version instances cannot migrate to earlier-version instances, e.g., a source instance of version 2012 cannot migrate to a target instance of version 2008. The target instance version must be greater than or equal to the source instance version for migration to occur. You can upgrade the target instance version using the  Adjusting Instance Version  feature in the console.
5
Backup jobs for the source instance cannot be disabled.
Please  submit a ticket  to get a solution.
6
Creating full backup files for the source database failed.
Creating full backup files for the source database failed:
1. Please execute net share in the cmd terminal of the source instance to check if a shared folder named backup exists.
2. Please check if the backup files are generated in the shared folder of the source instance.
3. Please check if the source instance does not have enough disk space to create a backup.
7
Source instance failed to transfer backup files.
Source instance failed to transfer backup files:
1. Please check if the file-sharing service is enabled on the source instance.
2. Please check if the system account beginning with "ls" is correctly created in the source instance.
3. Please execute net share in the cmd terminal of the source instance to check if a shared folder named "backup" exists.
4. Please check if the system account beginning with "ls" has full control permissions for the shared folders.
8
Failed to recover the database using the backup file on the target instance.
Failed to recover the database using the backup file on the target instance:
1. Please check if the file-sharing service is enabled on the source instance.
2. Please check if the system account beginning with "ls" has been correctly created in the source instance.
3. Please execute net share in the cmd terminal of the source instance to check if a shared folder named 'backup' exists.
4. Please check if the system account beginning with "ls" has full control permissions for the shared folders.
9
Incremental synchronization deployment failed.
Please  submit a ticket  to get a solution.
10
Failed to synchronize incremental logs.
Failed to synchronize incremental logs:
1. Network connectivity exception occurs during synchronization and sharing incremental files failed. Please redo the migration.
2. During incremental migration, transaction logs were truncated. Please stop the log backup job on the source instance and redo the migration.
11
After synchronization, data inconsistency exists.
After synchronization, data inconsistency exists. Full backup data synchronization has been completed. Please manually check the migrated data. If there are significant data differences, re-migration is required. The possible causes of data inconsistency are as follows:
1. The source database was not stopped for writes: Before clicking "Complete" for the task, the source database needs to be stopped for writes for 3-5 minutes to avoid data verification inconsistencies.
2. Incremental log synchronization failure: During incremental synchronization, log backup and log truncation operations on the source instance need to be stopped.

ヘルプとサポート

この記事はお役に立ちましたか？

営業担当者にお問い合わせいただくかチケットを提出してサポートを求めることができます。

フィードバック

tencent cloud

Data Transfer Service

Error Handling

Problem Scenario

Problem Handling

ヘルプとサポート

Serial Number	Error Message	Suggestions
1	Task failed. Please submit a ticket to get a solution.	Please submit a ticket to get a solution.
2	The database to be migrated was not found in the source instance.	The database to be migrated was not found in the source instance. Please confirm whether the database to be migrated exists in the source instance.
3	The migration initialization operation cannot be performed on the source instance.	The migration initialization operation cannot be performed on the source instance: 1. Please check if the SQL service startup account for the source instance is using the built-in Local System account. You need to select "Built-in account" in "Log on as" in the startup configuration and modify it to start with the Local System account. 2. Please check if the source instance has xp_cmdshell enabled. You need to enable xp_cmdshell. 3. Please ensure that the migration account has sysadmin permissions.
4	Later-version instances cannot migrate to earlier-version instances.	Later-version instances cannot migrate to earlier-version instances, e.g., a source instance of version 2012 cannot migrate to a target instance of version 2008. The target instance version must be greater than or equal to the source instance version for migration to occur. You can upgrade the target instance version using the Adjusting Instance Version feature in the console.
5	Backup jobs for the source instance cannot be disabled.	Please submit a ticket to get a solution.
6	Creating full backup files for the source database failed.	Creating full backup files for the source database failed: 1. Please execute net share in the cmd terminal of the source instance to check if a shared folder named backup exists. 2. Please check if the backup files are generated in the shared folder of the source instance. 3. Please check if the source instance does not have enough disk space to create a backup.
7	Source instance failed to transfer backup files.	Source instance failed to transfer backup files: 1. Please check if the file-sharing service is enabled on the source instance. 2. Please check if the system account beginning with "ls" is correctly created in the source instance. 3. Please execute net share in the cmd terminal of the source instance to check if a shared folder named "backup" exists. 4. Please check if the system account beginning with "ls" has full control permissions for the shared folders.
8	Failed to recover the database using the backup file on the target instance.	Failed to recover the database using the backup file on the target instance: 1. Please check if the file-sharing service is enabled on the source instance. 2. Please check if the system account beginning with "ls" has been correctly created in the source instance. 3. Please execute net share in the cmd terminal of the source instance to check if a shared folder named 'backup' exists. 4. Please check if the system account beginning with "ls" has full control permissions for the shared folders.
9	Incremental synchronization deployment failed.	Please submit a ticket to get a solution.
10	Failed to synchronize incremental logs.	Failed to synchronize incremental logs: 1. Network connectivity exception occurs during synchronization and sharing incremental files failed. Please redo the migration. 2. During incremental migration, transaction logs were truncated. Please stop the log backup job on the source instance and redo the migration.
11	After synchronization, data inconsistency exists.	After synchronization, data inconsistency exists. Full backup data synchronization has been completed. Please manually check the migrated data. If there are significant data differences, re-migration is required. The possible causes of data inconsistency are as follows: 1. The source database was not stopped for writes: Before clicking "Complete" for the task, the source database needs to be stopped for writes for 3-5 minutes to avoid data verification inconsistencies. 2. Incremental log synchronization failure: During incremental synchronization, log backup and log truncation operations on the source instance need to be stopped.