| Bug #30929 | Replication fails with error 1366 on slave | ||
|---|---|---|---|
| Submitted: | 10 Sep 2007 11:57 | Modified: | 23 Jan 2008 8:32 |
| Reporter: | Antonio Trindade | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
| Version: | 5.0.41 | OS: | Windows (2003 R2) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | 1366, replication, slave | ||
[10 Sep 2007 13:21]
MySQL Verification Team
Thank you for the bug report. Could you please provide: - The master and slave my.ini files. - Create table statement. - The insert statement which causes the issue. Thanks in advance.
[10 Sep 2007 14:43]
Antonio Trindade
Slave and master ini
Attachment: my.zip (application/zip, text), 8.07 KiB.
[10 Sep 2007 14:49]
Antonio Trindade
I send you the script of the table pagamentos that is indicated on the error and of the table pagamentoslog that was the column autor the possible one refered on the error message. The query is indicated on the error message. Thanks,
[12 Sep 2007 15:29]
Antonio Trindade
Hello, i test the replication with the same data on 2 Linux (Fedora - Master | Debian - slave) both with the version 5.0.45 and the result was the same. I think that the column name on the error is wrong but the query is that one. Thanks,
[17 Sep 2007 17:33]
Antonio Trindade
Hello, apparently the problems is in the use of the variable "USER()" on a trigger of the table pagamentos that is trying to write on the user name on a column "autor". Thanks,
[23 Jan 2008 8:32]
Sveta Smirnova
Thank you for the report. Closed as "Not a Bug" according to last comment.
Description: I'm trying to implement replication but the slave stops with error: Error 'Incorrect string value: '\xE7\xFFJ\xA6\xFD\x82...' for column 'autor' at row 1' on query. Default database: 'mydb'. Query: 'insert into pagamentos ...' The problem is that there is no column autor on table pagamentos. I think that the slave is getting "confuse" when it reads the master bin logs, maybe it is trying to read the file with a incorrect code page or not ... I have a column 'autor' in other table that was created with the default character set latin1 for that column. The slave machine was create from a clone of the master machine and the only thing that i changed was the master parameter on the slave. The default character set on both is mysql> show variables like 'char%'; +--------------------------+---------------------------------------------------------+ | Variable_name | Value | +--------------------------+---------------------------------------------------------+ | character_set_client | utf8 | | character_set_connection | utf8 | | character_set_database | utf8 | | character_set_filesystem | binary | | character_set_results | utf8 | | character_set_server | utf8 | | character_set_system | utf8 | | character_sets_dir | C:\Program Files\MySQL\MySQL Server 5.0\share\charsets\ | +--------------------------+---------------------------------------------------------+ 8 rows in set (0.00 sec) The code page is: Active code page: 850 Error: 070907 17:46:36 [ERROR] Slave: Error 'Incorrect string value: '\xE7\xFFJ\xA6\xFD\x82...' for column 'autor' at row 1' on query. Default database: 'mydb'. Query: 'insert into pagamentos(insid, tipopagid, estadopagid, mbref, mbentidade, cctipo, ccano, ccmes, ccnome,cccodigo, ccdigcontrole, ccref, cccodresposta, ccdatahora, chqnumero, quantia, dataenvfact, createdate) values ( NAME_CONST('in_insid',29300), NAME_CONST('in_tipopagid',10), NAME_CONST('in_estadopagid',1), NAME_CONST('in_mbref',NULL), NAME_CONST('in_mbentidade',NULL), NAME_CONST('in_cctipo',NULL), NAME_CONST('in_ccano',NULL), NAME_CONST('in_ccmes',NULL), NAME_CONST('in_ccnome',NULL), NAME_CONST('in_cccodigo',NULL), NAME_CONST('in_ccdigcontrole',NULL), NAME_CONST('in_ccref',NULL), NAME_CONST('in_cccodresposta',NULL), NAME_CONST('in_ccdatahora',NULL), NAME_CONST('in_chqnumero',NULL), NAME_CONST('in_quantia',0.00), NAME_CONST('in_dataenvfact',NULL), NAME_CONST('cdate',_binary'2007-09-07 08:28:17'))', Error_code: 1366 How to repeat: Implement replication using the database character set utf8 and some columns in latin1.