Comments on: How To Fix MySQL Replication After an Incompatible DDL Command https://www.percona.com/blog/how-to-fix-mysql-replication-after-an-incompatible-ddl-command/ Wed, 27 May 2020 06:08:58 +0000 hourly 1 https://wordpress.org/?v=6.5.2 By: bowranger https://www.percona.com/blog/how-to-fix-mysql-replication-after-an-incompatible-ddl-command/#comment-10972267 Wed, 27 May 2020 06:08:58 +0000 https://www.percona.com/blog/?p=52668#comment-10972267 Sorry but this does not work at all. Tried with 2 servers. The error reset back to the earliest point after changing master_auto_position = 1 in 2nd last step.

]]> By: bowranger https://www.percona.com/blog/how-to-fix-mysql-replication-after-an-incompatible-ddl-command/#comment-10972266 Wed, 27 May 2020 05:48:05 +0000 https://www.percona.com/blog/?p=52668#comment-10972266 After changing “CHANGE MASTER TO MASTER_AUTO_POSITION=1;”, the error fall back to 1064 again with same error (restore to the earliest error point). what happen ?

]]> By: geofreyr https://www.percona.com/blog/how-to-fix-mysql-replication-after-an-incompatible-ddl-command/#comment-10971729 Sat, 25 Jan 2020 12:53:23 +0000 https://www.percona.com/blog/?p=52668#comment-10971729 I think this line is incorrect:

“The next binary log position is 36174621. To fix the slave, run:”

]]> By: Subhajit https://www.percona.com/blog/how-to-fix-mysql-replication-after-an-incompatible-ddl-command/#comment-10969758 Mon, 01 Oct 2018 13:10:24 +0000 https://www.percona.com/blog/?p=52668#comment-10969758 Great article. Thank you!

]]>