Hello.
Please, send the output of the following statement executed both on master and slave: show variables like '%char%'; Send the definition of your table as well: SHOW CREATE TABLE sum_day_key_requests; Marco P$hler <[EMAIL PROTECTED]> wrote: > Hi, > > I try to replicate an existing database to a new server and run into > trouble with collations. Maybe somebody can help me. > > Existing DB-Server (Master): > MySQL Version 4.1.12 > ca. 100 GB Database size. > > New DB-Server (Slave): > MySQL Version 4.1.12 > > Here is what I did to get the replication up and running: > > - Shutdown MySQL on the Master > - Copy the MySQL datadir from the Master to the Slave (approx. 4 > hours :-) > - Startup the Master again and execute RESET MASTER to delete the > existing binlogs. > - Startup the Slave > > The Slave starts the replication, as I can see using SHOW PROCESSLIST on > the Slave. Afer a while the following error occured listed in > the .err-file. > > 050808 10:41:25 mysqld started > 050808 10:41:27 InnoDB: Started; log sequence number 70 1628293808 > /usr/sbin/mysqld: ready for connections. > Version: '4.1.12-standard-log' socket: '/var/lib/mysql/mysql.sock' > port: 3306 MySQL Community Edition - Standard (GPL) > 050808 10:42:11 [Note] Slave SQL thread initialized, starting > replication in log 'FIRST' at position 0, relay log > './HAL2006-relay-bin.000001' position: 4 > 050808 10:42:11 [Note] Slave I/O thread: connected to master > '[EMAIL PROTECTED]:3306', replication started in log 'FIRST' at > position 4 > 050808 11:49:23 [ERROR] Slave: Error 'Illegal mix of collations > (latin1_bin,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '='' > on query. Default database: 'report'. Query: 'UPDATE > sum_day_key_requests SET sum = sum + 1 WHERE day = '2005-7-30' AND type > = 'redirect' AND client = '7865' AND channel = '78' AND campaign = 'DE > Conversion' AND grouping = 'Flirt- und Kontaktb$rse' AND `key` = 'Flirt > Kontakte' AND afftraf = 'NULL'', Error_code: 1267 > 050808 11:49:23 [ERROR] Error running query, slave SQL thread aborted. > Fix the problem, and restart the slave SQL thread with "SLAVE START". We > stopped at log 'HAL2005-bin.000003' position 27769229 > > The only idea, which came into my mind, is that the server use different > default charsets or collations. I checked the configurations and can't > find a difference. Is there a possibility to check the default charsets > and collations on the running server ? > > thanks in advance > > Marco > > --- > http://www.tuxoo.de > http://www.kontaktlinsen-preisvergleich.de > > > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
