Full Phase Error: Failed to add the foreign key constraint '***' to system tables
Scenarios
During a full migration or synchronization, an error is reported, and the log information is as follows: Failed to add the foreign key constraint '***' to system tables
Possible Causes
During the full phase, the destination database has foreign key constraints with the same name.
Solution
- Run the following SQL statement to delete or rename the foreign key constraints with the same name in the destination database:
select * from information_schema.REFERENTIAL_CONSTRAINTS where CONSTRAINT_NAME = "foreign_key_name";
- In the task list, locate the target task and click Resume in the Operation column to resume the task.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot