Solution: check the above causes and make adjustments accordingly.
Solution: check whether there are large transactions or batch processing operations. If the delay persists after a period of time, please contact us for troubleshooting.
Possible causes: write lock is not enabled for the target instance and some additional data is written to it; the corresponding table may lack a primary key; therefore, when the sync tool sends a request again, part of the data will be written to the target instance again.
Solution: add a primary key to the source table, delete existing data from the target table, and sync the data again. Or, you can manually delete extra data from the target table.
Data sync does not lock the target database, which can still be read from/written to normally. Therefore, please manipulate the target database with caution.
Possible causes: the source and target databases are on different versions, leading to differences in DDL syntax.
Solution: manually run the DDL statements again in the target database.
Possible causes: the account required by sync or the table structure of the target database is modified.
Solution: pause the sync task, modify the corresponding account, change the table structures of the target and source databases to the same, and perform sync again.