This topic describes how to fix the issue if full data migration stops or slows down.

Issue

When DTS is performing full data migration, the migration takes a long time or stops.

Solution

Use the following methods to troubleshoot the issue:

  • Check the source database:
    • Estimate the migration time: Check the data volume of the objects to be migrated from the source database.
    • Check concurrent tasks: Check whether multiple tasks run at the same time.
      Note Concurrent tasks may result in temporary resource shortage. We recommend that you run tasks in separate time periods.
    • Check whether the username and password of the source database are accurate.
    • Check whether the whitelist settings are valid. For more information, see Whitelist DTS IP ranges for your user-created database.
    • Check whether all large tables in the source database contain primary keys or unique indexes.
      Note If the source database contains only common indexes or no indexes, large amounts of data may be generated.
  • Check the destination database:
    • Check whether the username and password of the destination database are accurate.
    • Check whether the whitelist settings are valid. For more information, see Whitelist DTS IP ranges for your user-created database.
    • Check whether the destination database instance is read-only.
      Note Data cannot be written to a read-only instance.
    • Check whether the destination database has available disk space.
    • Check whether the performance of the destination database has reached the bottleneck.
    • Check whether the destination database has deadlocks.
      Note If the destination database has deadlocks, data cannot be written to the database.
  • Check the network connectivity and whether the network bandwidth is limited. We recommend that you upgrade the network bandwidth if necessary.