On Wed, 2007-10-17 at 21:16 +0200, Oded Arbel wrote: > The problem is that on the second server everything looks peachy - > information is coming in and its always up to date, but on the third > server on the renamed database one of the log tables is not getting any > updates - currently it is stuck with records from yesterday at noon and > nothing new is coming in (I currently think its only one that has > problems, but I haven't checked all of them). Other tables are getting > updates just fine.
The problem was - as usual - RTFM. The MySQL "replicate-rewrite-db" option, its important to know, is not resolving names using the actual data being changed and not even by parsing the SQL query that did the update - but only based on the current database select using the 'use' statement. The problem was that the table I had problem with (unlike all other tables) has data inserted using something like this: use my_db; insert into my_db.my_table (columns...) values (values...) This was enough to brake replicate-rewrite-db. Except for fixing the offending application, I don't know what else can be done. Funny though, if the rewrite command is replicate-rewrite-db=my_db->other_db and then I add replicate_do_table=my_db.my_table then updates to my_db.my_table on the origin server cause my_db.my_table on the replicating server to update, and not other_db.my_table. -- Oded ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
