Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Unexpected Error With Db Synchronization Wizard

forums forums SQLyog Sync tools, Migration, Scheduled Backup and Notifications Unexpected Error With Db Synchronization Wizard

  • This topic is empty.
Viewing 1 reply thread
  • Author
    Posts
    • #10625
      fhx
      Member

      Greetings,

      I have a problem with the sync of a database (WordPress DB – Version 2.3.1) from a remote server (done via HTTP tunneling) and my local MySQL DB (both sides 4.1). I use SQLyog Enterprise 6.1.

      Via the Powertools and the “Database Synchronization Wizard” I created a sync task (one direction) — simply by activating the tables to be synchronized. Finally I get the following error in the interface:

      Quote:
      SQLyog Job Agent Version 6.1

      Copyright©Webyog Softworks Pvt. Ltd.. All Rights Reserved.

      Sync started at Sat Nov 10 22:44:22 2007

      Table SrcRows TgtRows Inserted Updated Deleted

      ========================= ======= ======= ======== ======= =======

      `st231_comments` 3 1 There was an error while execute a query. The query and the error has been logged in the log file.

      `st231_links` 7 7 There was an error while execute a query. The query and the error has been logged in the log file.

      `st231_postmeta` 0 0 0 0 0

      `st231_posts` 2 2 There was an error while execute a query. The query and the error has been logged in the log file.

      `st231_term_relationships` 8 8 0 0 No change

      `st231_term_taxonomy` 2 2 There was an error while execute a query. The query and the error has been logged in the log file.

      `st231_terms` 2 2 There was an error while execute a query. The query and the error has been logged in the log file.

      `st231_usermeta` 17 9 There was an error while execute a query. The query and the error has been logged in the log file.

      `st231_users` 3 2 There was an error while execute a query. The query and the error has been logged in the log file.

      The log file provides a little bit more info:

      Quote:
      `st231_comments` 3 1 Error No. 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ',`comment_post_ID`,`comment_author`,`comment_author_email`,`comm 1st Phase : 0 0

      I am certain that the DB Name, DB Engine: “MyISAM”; and the collation:”latin1_swedish_ci” are on both sides the same. Additionally: the names of the columns are the same as I have installed on both sides the same WordPress version with the same settings.

      What is astonishing is that “st231_postmeta” and “st231_term_relationships” is working.

      Why do I get a 1064 Error?

      Any hint is highly appreciated.

      Does anyone have a workaround a another method to do a sync?

      Best,

      Frank

    • #25259
      peterlaursen
      Participant

      I recall that we have had a few issues with that WORDPRESS system – but do not recall details. But you should not expect us to know about or support other applications. We relate to the database and the content of the database alone! We have no clew about the contents of the milllions of applications around .. you will have to inform us!

      If the structure (column types and order, charset, storage engine etc.) on both sides are not identical the sync will refuse to start! Once it has started it should finish.

      Can you provide a test case with a zipped dump from both servers. You can crate a ticket if you want privacy. And please not much too big! In principle a single row that fails to sync is enough!

      Alternative provide download links and a step-by-step instruction on how to reproduce this!

      Also tell the EXACT server versions! Not 4.1 but 4.1.10 or 4.1.22 … and both source and target.

      I also think you should try 6.12. Just to be sure .. but frankly I do not think this is an issue that has been resolved between 6.1 and 6.12!

Viewing 1 reply thread
  • You must be logged in to reply to this topic.