Changes between Version 49 and Version 50 of Replication_Issues

Timestamp:

Mar 12, 2012, 1:36:58 PM (14 years ago)

Author:

Serge CHASTEL

Comment:

--

Replication_Issues

@@ -9 +9 @@
 From Bill: "I did use the table in an update last night. That was a one time command. The reason that the table is not in gpc1 is that I'm not finished with it yet and I didn't want to cause problems with replication. Apparently using it for a table update caused a problem."
 
-I ran the usual {{{STOP SLAVE; SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; START SLAVE;}}} on both hosts to fix the problem.
-
+I ran the usual {{{STOP SLAVE; SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; START SLAVE;}}} on ippdb03.
+
+It looks though that there are other problems (multiple insert attempts for the same pk) for ipp001.
 
 = 20120223/08:40: ippdb03 =