MySQL Bugs: #19269: Replication slave stops when encountering a German Umlaut character

Bug #19269	Replication slave stops when encountering a German Umlaut character
Submitted:	21 Apr 2006 23:20	Modified:	25 Apr 2006 9:33
Reporter:	Ben Damer	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	Ver 14.12 Distrib 5.0.20	OS:	Linux (Debian/Testing)
Assigned to:		CPU Architecture:	Any

Description:
I have a system with 2 Debian servers running, one acts as the replication master and one as the slave, otherwise the two are identical.

Recently I upgraded both mysql servers from version 4 to version 5.0. Now, whenever the replication slave encounters a German Umlaut character, it stops. Here is a piece from my daemon.log:

Apr 21 22:43:27 phobos mysqld[16171]: 060421 22:43:27 [ERROR] Slave: Error 'Unknown column 'berufstÃ¤tig' in 'field list'' on query. Default database: 'database'. Query: 'Update probanden SET berufstätig='Teilzeit' where probanden_id='0009686'', Error_code: 1054
Apr 21 22:43:27 phobos mysqld[16171]: 060421 22:43:27 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.000002' position 4164

As you can see, the 'ä' character in the column name is the cause of this problem.

How to repeat:
In an existing replication system, create a database that contains umlaut-characters in the column names. Then instruct the salve to get data from the master server.

Thank you for a problem report. Please, send the my.cnf content from both master (is it also 5.0.20?) and slave. Describe you upgrade procedure (did you perform dump in 4.x.y and restore in 5.0.20, as it is recommended?). 

SHOW CREATE TABLE probanden;

results can be also useful.

I was able to fix the problem by setting language in both my.conf files to german (which apperantly was not neccessary in 4.x). Sorry, I hope I did not cause anyone unnecessary work.

So, it is not a bug.