Help Center> Data Replication Service> Troubleshooting> Failure Cases> Real-Time Migration and Synchronization from MySQL to MySQL> Full or Incremental Phase Error: binlog is not existed

Updated on 2022-09-21 GMT+08:00

View PDF

Full or Incremental Phase Error: binlog is not existed

Scenarios

During a full or incremental migration or synchronization, an error is reported, and the log information is as follows: service LOGMANAGER failed, cause by: binlog is not existed

Possible Causes

The possible causes are as follows:

The binlog files in the source database were deleted. DRS cannot obtain logs from the source database.

Solution

Recreate a DRS task.

Parent topic: Real-Time Migration and Synchronization from MySQL to MySQL

Previous topic: Full Phase Error: Access denied for user %s

Next topic: Full or Incremental Phase Error: Can not read response from server

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel