tencent cloud

TencentDB for SQL Server

Release Notes and Announcements
Release Notes
Product Announcements
User Guide
Product Introduction
Overview
Product Architecture
Strengths
Use Cases
Regions and AZs
Major Version Lifecycle Explanation
Features and Differences
Instance Types
Instance Specifications
Storage Types
Common Concepts
Network Environment
License Statement
Purchase Guide
Billing Overview
Product Pricing
Purchase Methods
Renewal Instructions
Payment Overdue
Refund
From Pay-as-You-Go to Monthly Subscription
Instance Adjustment Fees Description
Local Backup Space Billing
Cross-Region Backup Billing
Viewing Bill Details
Getting Started
Creating TencentDB for SQL Server Instance
Connecting to TencentDB for SQL Server Instance
Managing TencentDB for SQL Server Instance
Operation Guide
Constraints and Limits
Usage Specifications and Suggestions
Maintaining Instance
Adjusting Instance Configuration
Read-Only Instance
Network and Security
Account Management
Database Management
Data Security
Parameter Configuration
Monitoring and Alarms
Backup and Restoration 
Log Management
Publish-Subscribe
SSIS
Data Migration (New)
Data Migration (Legacy)
Data Synchronization (DTS) 
Practical Tutorial
TencentDB for SQL Server Methods for Regular Maintenance
TencentDB for SQL Server Optimization of Slow SQL
How to Better Use Tempdb
Cross-Account Backup Restoration
Creating VPC for TencentDB for SQL Server
Connecting Kingdee K/3 WISE to TencentDB for SQL Server
Account Permissions and Permission Control
Enabling and Disabling the CDC Feature
Shrinking a Database
API Documentation
History
Introduction
API Category
Making API Requests
Sales and fee related APIs
Instance Management related APIs
Operation and maintenance management related APIs
Network management related APIs
Account management related APIs
Database management related APIs
Security group management related APIs
Data security encryption related APIs
Parameter configuration related APIs
Extended Event related APIs
Log management related APIs
Read only instance management related APIs
Publish and subscribe related APIs
Backup related APIs
Rollback related APIs
Data migration (cold standby migration) related APIs
SQL Server Integration Services (SSIS) related APIs
Data migration (DTS old version) related APIs
Data Types
Error Codes
FAQs
Overview
Model Selection
Pricing and Selection
Connection and Network
Account and Permission
Backup and Rollback
Data Migration
Publish/Subscribe
Read-Only Instance
Version and Architecture Upgrade
Disk Space and Specification Adjustment
Monitoring and Alarms
Log-Related
Parameter Modification
Features
Performance, Space, and Memory-Related FAQs
Service Agreement
Service Level Agreement
Terms of Service
Performance Evaluation
Performance Test Report
Glossary
Contact Us

Error Handling

PDF
Focus Mode
Font Size
Last updated: 2024-07-31 09:39:35

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.

Help and Support

Was this page helpful?

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

Feedback