Monthly Archives: April 2012

restart mysql master/slave synchronisation after an invalid SQL query

you may encounter stuff like this:

a SQL clause that returns different error codes on master and slave, for instance if you use different versions of mysql:

[ERROR] Slave SQL: Query caused different errors on master and slave. Error on master: ... Error on slave:

To restart synchronisation simply skip that SQL clause this way:

SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1;

Of course the 1 may be replaced with “n” if you want to skip multiple SQL clauses.