[db Synchronisation] Skips Copying Specific Data

[Cis]

I have a problem with synchronizing two databases. Lets say DB-orig and DB-copy, to make it easy 🙂

Every 5 minutes I synchronize the database, which means: the data from DB-orig is copied to DB-copy (one way sync). The primary key in the table is a timestamp. This goes quite well.

BUT: every day, the data from 23:04 to 0:00 (11:04 pm to 0:00 am) is NOT copied. So every day, there's one hour missing in the target database.

I've tried to do the synchornization manually, but even then the data of 11:00-0:00 is not copied. The only way that DOES work, is an export from the DB-orig as *.SQL. And then import the data from 11:00-0:00 to the DB-copy. In this way, I do get an exact copy of the DB-orig.

Of course this is not the way to do it. Are there any known issues about this, or better: is there a solution?

DB-orig: MySQL 4.1.8

DB-copy: MySQL 4.0.28

[attachment=487:attachment]

(as you can see, in the DB-copy all the results from 23:02 to 0:04 are skipped)

[peterlaursen]

What is the SQLyog version that you are using?

There was an issue fixed with TIMESTAMPs early in the 5.x tree

But it is not supposed to work with TIMESTAMPs across MySQL 4.0 and 4.1

Please read:

http://webyog.com/faq/11_68_en.html

actually it surprises me that it works to 'some degree'

[Cis]

peterlaursen wrote on Jun 23 2006, 10:47 AM:

What is the SQLyog version that you are using?

There was an issue fixed with TIMESTAMPs early in the 5.x tree

But it is not supposed to work with TIMESTAMPs across MySQL 4.0 and 4.1

Please read:

http://webyog.com/faq/11_68_en.html

actually it surprises me that it works to 'some degree'

Thank you for your answer.

The version of SQLyog I use, is 5.12.

I'm doing the synchronization now for about 3 weeks, and every day the data between 23:00 and 0:00 is skipped. I does not matter if I do a scheduled sync or a manual sync. The synchronisation between 0:00 and 23:00 works perfectly. Exporting and importing an SQL-file *does* work.

What I can do, is install MySQL to another PC (newest mySQL version) to check if it has the same probs. In that case, it would be (or not be 😉 ) a version-problem

[peterlaursen]

I am not sure myself! An it indeed looks weird.

If you can produce some kind of test-case (table def's + a few data) I would like to work on it too.

You can attach it here or create a ticket.

[Author]

Posts