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

SJA won't do regular syncs

  • This topic is empty.
Viewing 4 reply threads
  • Author
    Posts
    • #8424
      shaunie
      Member

      Hi,

      I have noticed that the sja.log file is only recording the 'forced synchronizations' ( Tools > Database synchronization wizard > Edit a saved synchronization session > Next > Next > Next > Synchronize now ).

      As a result I have now noticed that there is no regular synchronization taking place even though I have set this up through the synchronization wizard.

      I have checked and double checked the settings, the only errors occuring in sja.log are for a few tables with no primary key defined and differing MySQL versions. This is irelavant however because the syncronisations work when they are forced, is this a problem with windows task manager perhaps?

      THanks for your help

    • #15760
      Ritesh
      Member

      Is there any spaces in the path of XML file?

      Remove all the spaces from the path of the XML file and then schedule it.

    • #15761
      shaunie
      Member

      Hi,

      Here is the path taken from the task manager window:

      “C:Program FilesSQLyogsja.exe” C:Program FilesSQLyogWMS_Backup.xml

      As you can see there are no spaces in the xml filename…

      Have you got any other suggestions?

      Thank you for your help 🙂

    • #15762
      shaunie
      Member

      Hi,

      I have noticed there was a space in the path and this has now been corrected, sorry!

      However I am still not able to synchronise, here is an example of the output from the CMD window upon synchronisation:

      SQLyog Job Agent Version 1.2

      Copyright © Webyog. All Rights Reserved.

      Sync started at Fri May 07 15:20:00 2004

      Warning : Source and Target MySQL versions are not matching.

      Source : 3.23.54, Target : 4.0.18-max-debug.

      SJA may not work properly because of the difference in behaviour of concat_ws()

      across multiple MySQL versions.

      Table SrcRows TgtRows Inserted Updated Deleted

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

      `Allocations` 100 100 0 80

      It just hangs here for five minutes then gives up.

      From reading earlier posts I gather that this might be because of conflicting mysql versions on the source and target. I originally installed 3.23.54 on the target to match the source version but because I am using windows 2000 on the target and unix as the OS on the source I had to upgrade to 4.0.18 on the target in order to alter the varibale 'lower_case_table_names' to 2 to avoid case sensitivity conflicts between the 2 operating systems. This feature was only introduced on 4.0.18 (http://dev.mysql.com/doc/mysql/en/Name_case_sensitivity.html)

      As I am unable to upgrade the mysql version on the source, does this mean I can't do database backups?

      Thanks for your help

    • #15763
      Ritesh
      Member
      Quote:
      SQLyog Job Agent Version 1.2

      Copyright © Webyog. All Rights Reserved.

      The latest version of SQLyog uses SJA 2.0. I will suggest that you first upgrade to SQLyog 3.7 and try out the sync process.

Viewing 4 reply threads
  • You must be logged in to reply to this topic.