DTS-150002:MySQL binlog filename @ offset is not exists. Original error: original_error -

Problem description

When you use DTS to migrate data, the following error message appears: the MySQL log does not exist.

DTS-1050002 MySQL binlog [$Position] is not exists. Original error: original_error.

Note:[$Position] is the Position of the Binlog file.

The possible causes of the error are as follows:

1. Data Migration tasks are suspended for more than seven days.
Drawback 2: logs are cleared due to a too short Binlog retention period in the source database.

Select a solution based on the cause of the problem.

Solution to Problem 1: If the data migration task is suspended for more than seven days, create a new data migration task. For more information, see create a data migration task.
Solution to Problem 2: if the corresponding Binlog files cannot be recovered and data migration is impossible, we recommend that you keep the MySQL logs in the source database for at least three days.
- RDS instance
  1. Log on to the RDS console and select a region.
  2. Click the instance name > Backup and restoration > Local backup settings. Set the time period as needed.
- User-created database
  - If your database is a user-created database, modify the retention period of binlogs. For more information, see MySQL official website.