[gh0st]

peterlaursen wrote on Apr 5 2006, 06:40 AM:

But if I understand you right, they don't disappear permanently?

correct, i am almost certain that this is an issue with mysql and not with sja

I have tried running myisamchk and isamchk with the repair options on all sql servers, both source and destination servers, I've even gone as far as droping the database, recreating it, and resync'ing it, still no luck.

I've used sja for quite some time, and have updated to the latest version with still no change. This same schema has been in place for a while, and never have had any problems with it until now.

baffled.

[gh0st]

What dissapears:

entire rows of data

I am using SQLyog Job Agent Version 4.0 with mysql version: 4.1.10a-standard-log across the board, on fedora core 2 linux. I have not tried sja 5.0 yet, ill give that a try

It could very well be a sql problem, if so it is one that I have been unable to figure out. I have tried running the myisamchk and isamchk utilities, to no avail

[gh0st]

so, its a feature then, not a bug

thanks 😉

[gh0st]

I am using two mysql servers version 4.1.10, both running on seperate servers running fedora core 2 linux

I am not using tunneling

I am using SQLyog job agent 4.0 on the primary sql server, running fedora core 2 linux

i cannot readily send a dump of our db as it contains passwords, i can send a dump of one of the tables which does infact have a primary key (in which sja reports that it does not)

if that would be enough, where would you like me to send the dump?

[Author]

Posts