Incremental Phase Error: Deadlock found when trying to get lock
Scenarios
During an incremental migration or synchronization, an error is reported, and the log information is as follows: service INCREMENT failed, cause by: record tid: %s,seqno: %s with PK applied failed in table %s, Deadlock found when trying to get lock; try restarting transaction
Possible Causes
The possible causes are as follows:
- A deadlock occurs in the destination database.
Solution
Contact destination database O&M engineers to check the status and load of the destination database.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.