forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › Tool is corrupting my database while syncing
- This topic is empty.
-
AuthorPosts
-
-
March 11, 2005 at 11:41 pm #8850firebrightMember
I'm moving VERY large (600+ M:cool: mysql databases with this tool, and it's actually corrupting my data. The copies are no good! I've no idea why it's happening, but this is the error I'm getting:
ERROR 1030: Got error 127 from table handler
How can this happen? I'm not even sure where to begin checking.
Thanks,
Frustrated in California
-
March 12, 2005 at 3:21 am #17155peterlaursenParticipant
Moving how ?? Do you use “copy DB to another host” or “syncronization” or just export/import sql ?? Does the connection involve some kind of tunnelling ?
What are the mysql server versions ?? Certain variable types (such as date/time , timestamp) are incompatible across older and more recent mysql versions. The error message could imply something like that.
Are the server configuration(s) under your control or not ?
Please explain about the data structure and possibly supply “create table” statements for the DB('s), and even some sample data. If you don't want to throw it here in public, you could wait for Ritesh to send him this information confidentially.
And you have no problems with small DB's ??
Do you know about a tool that works ?
-
March 12, 2005 at 6:31 am #17156RiteshMember
SJA, the data synchronization tool of SQLyog executes only valid SQL statements to find differences and bring the two databases in sync with each other.
Are you sure that its the query(s) that SJA executes corrupting the data?
-
March 14, 2005 at 7:39 pm #17157firebrightMember
Thanks for the detailed questions. I'll do my best to reply…
> Moving how ?? Do you use “copy DB to another host” or “syncronization” or just export/import sql ?? Does the connection involve some kind of tunnelling ?
Sync. Exporting and importing is too resource intensive, and the mysqld db dies trying to do it. There is no tunnel.
> What are the mysql server versions ?? Certain variable types (such as date/time , timestamp) are incompatible across older and more recent mysql versions. The error message could imply something like that.
3.23. Yes, I know it's old. No, there is nothing I can do about it.
> Are the server configuration(s) under your control or not ?
Some of them.
> Please explain about the data structure and possibly supply “create table” statements for the DB('s), and even some sample data. If you don't want to throw it here in public, you could wait for Ritesh to send him this information confidentially.
I cannot share this info unfortunately. It's for a company, and involved financial information. 😉
> And you have no problems with small DB's ??
None.
> Do you know about a tool that works ?
No, haven't found one. rsync. 😉
> Are you sure that its the query(s) that SJA executes corrupting the data?
Yes, fairly. It's a fresh copy to a new db, and it's showing errors. Myisamchk on the donor host shows no errors…
This is the job I have scheduled…
root 3306 foo localhost root 3306 foo I was as miffed about it as you guys seem to be… I couldn't figure how it could end up corrupted, but it does. It literally ends up with corrupted DBs (myisamchk reveals) even though rsyncing the EXACT same dbs over has no errors. So, I'm 100% sure it's the tool.
-
March 14, 2005 at 7:53 pm #17158RiteshMember
As mentioned earlier, SQLyog just sends a bunch of SQL statements to the MySQL server.
You need to help us in pin-pointing the exact SQL that is causing this corruption so that we can get MySQL AB Support involved.
To help us reproduce the error at our end, you need to send some sample data OR do it yourself by logging the queries.
-
-
AuthorPosts
- You must be logged in to reply to this topic.