tencent cloud

PrevNext

Feedback

search by keyword

Recent Pages

Documentation
TencentDB for SQL Server
    Documentation
    Download PDF

    Error Handling

    Last updated: 2024-07-31 09:39:35
    Download PDF

      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.
      Contact Us

      Contact our sales team or business advisors to help your business.

      Contact Us
      Technical Support

      Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

      Submit a Ticket
      7x24 Phone Support
      Copyright © 2013-2024 Tencent Cloud. All Rights Reserved.
      Privacy PolicyLegalCookie Policy