forums › forums › SQLyog › Sync tools, Migration, Scheduled Backup and Notifications › Sync error 1065
- This topic is empty.
-
AuthorPosts
-
-
March 23, 2004 at 12:40 pm #8377jbatyMember
I've been synching a database for a few days now with no problems. This morning I ran the same job and received the following:
Error No. 1065
Query was empty
Is there some sort of verbose logging that would better indicate the cause of this?
-
March 23, 2004 at 12:45 pm #15596ShadowMember
Take a look at the history pane. You may find answer to your question!
-
March 23, 2004 at 12:48 pm #15597ShadowMember
Hmmm, apparently a string containing only spaces (or nothing at all) was passed to the server for some reason. Can you find such query in the history pane?
-
March 23, 2004 at 1:30 pm #15598jbatyMember
I was running it from the command line (windows), so there's no history. I tried running it from within SQLyog but there's nothing relevant in the history pane that I can see. In fact there's nothing at all in the history pane that indicates that I ran a synch job.
Am I looking in the wrong place?
-
March 23, 2004 at 1:54 pm #15599ShadowMember
No. What about sja.log? Should be located in the same directory where sja.exe is placed.
-
March 23, 2004 at 2:18 pm #15600jbatyMember
sja.log is where I found the original error message:
Error No. 1065
Query was empty
The thing I have been ignoring is the difference in MySQL versions.
Warning : Source and Target MySQL versions are not matching.
Source : 4.0.15-standard, Target : 4.0.18-max-debug-log.
SJA may not work properly because of the difference in behaviour of concat_ws() across multiple MySQL versions.
Thought I'd mention that, although I'm synching several databases with the same version differences without any apparent problems.
Thanks for your help with this.
-
March 24, 2004 at 3:31 am #15601RiteshMember
Can you send us a backup of both the databases?
The error is not occuring due the difference of MySQL versions.
-
March 24, 2004 at 10:08 pm #15602ShadowMember
concat_ws() function was changed in the 4.0.14 version, so this cannot be the reason of the failure of the sync. Can you think of any changes made to the dbs in question?
-
-
AuthorPosts
- You must be logged in to reply to this topic.