WebHosting

Sunday, November 10, 2013

MySQL: Replication - Skip sql statement from execution

In any MySQL Replication set up, some or the other time we come across errors on the Slave due to which, replication stops.  

If the error is due to manual intervention on replication, we may have to skip the current SQL transaction on Slave which caused the error.

In the case, below is the command to be executed:

SET GLOBAL sql_slave_skip_counter=1;
START SLAVE;



You can increase the counter value if you want to skip multiple consecutive transactions.

Featured Posts

Error Message in DBeaver connecting using jdbc: Public Key Retrieval is not allowed

Fixing “Public Key Retrieval is not allowed” Error in MySQL with DBeaver   If you are trying to connect MySQL 8+ with DBeaver and suddenly...