Hi,
Apologies for not posting this in the 'replication' list, but that seems
not very active...
I have setup replication between two 4.1.10 databases, and I noticed
that the SLAVE THREAD had stopped because of an SQL error.
The errorlog says: Fix the problem and restart the slave SQL thread.
Hello.
May be it is easier just to setup replication again, without
importing to the slave parts of the master's binary log. But,
certainly, you should find out the statement which produced
the error, to prevent similar problems in future.
Martijn van den Burg wrote:
Hi,
