Full Synchronization Error: relation *** does not exist
Scenarios
During full synchronization, an error is reported, and the log information is as follows: service DATAMOVE failed, cause by: ERROR: relation '%s' does not exist Position: 15
Possible Causes
During table-level synchronization, objects with dependencies are not synchronized. For example, the source database contains tables A and B and table A depends on table B, but only table A is synchronized.
Solution
- Clear data in the destination database.
- Create a synchronization task again and select the objects to be synchronized and all dependent objects.
- Start the synchronization task.
What is your overall rating for this page?
Thank 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