Changes between Version 56 and Version 57 of Replication_Issues

Timestamp:

May 30, 2012, 10:25:56 AM (14 years ago)

Author:

Serge CHASTEL

Comment:

--

Replication_Issues

@@ -185 +185 @@
 I applied {{{STOP SLAVE; SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1; START SLAVE;}}} four times and everything looks fine now.
 (Messages were like: 'Duplicate entry ...')
-= 20110429/0850: gpc1 Replication Error =
+== 20110429/0850: gpc1 Replication Error ==
 From mysql slave on ippc02 (SHOW SLAVE STATUS)
 Query partially completed on the master (error on master: 1317) and was aborted. There is a chance that your master is inconsistent at this point. If you are sure that your master is ok, run this query manually on the slave and then restart the slave with SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; START SLAVE; . Query: 'drop table lapExp'.