Bug #62541 NAME_CONST('in_keyRef',_utf8'gT8nm3rWD+eILdXphATJ/w==') ERROR
Submitted: 26 Sep 2011 9:53 Modified: 27 Oct 2011 4:44
Reporter: Anil Alpati Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S4 (Feature request)
Version:5.1.23 OS:Any
Assigned to: CPU Architecture:Any

[26 Sep 2011 9:53] Anil Alpati
Description:
Below is my replication errror in slave 

 Last_SQL_Errno: 1210
               Last_SQL_Error: Error 'Incorrect arguments to NAME_CONST' on query. Default database: 'rsip_db30'. Query: 'INSERT reputation_hist_ip (keyRef, bucketId, tagValue, dataValue, tStamp) VALUES ( NAME_CONST('in_keyRef',_utf8'gT8nm3rWD+eILdXphATJ/w==' COLLATE 'utf8_general_ci'),  NAME_CONST('in_bucketId',14430),  NAME_CONST('in_tag1Value',5),  NAME_CONST('in_data3Value',_binary'0x00000001410000000000000000000000014E800DC200000000' COLLATE 'binary'),  NAME_CONST('in_tStamp',1317021188))'

Master  : 5.1.40-log
Replication  : 5.1.23-rc-log

What can be done 

How to repeat:
Below is my replication errror in slave 

 Last_SQL_Errno: 1210
               Last_SQL_Error: Error 'Incorrect arguments to NAME_CONST' on query. Default database: 'rsip_db30'. Query: 'INSERT reputation_hist_ip (keyRef, bucketId, tagValue, dataValue, tStamp) VALUES ( NAME_CONST('in_keyRef',_utf8'gT8nm3rWD+eILdXphATJ/w==' COLLATE 'utf8_general_ci'),  NAME_CONST('in_bucketId',14430),  NAME_CONST('in_tag1Value',5),  NAME_CONST('in_data3Value',_binary'0x00000001410000000000000000000000014E800DC200000000' COLLATE 'binary'),  NAME_CONST('in_tStamp',1317021188))'

Master  : 5.1.40-log
Replication  : 5.1.23-rc-log

What can be done
[26 Sep 2011 11:05] Valeriy Kravchuk
You should never use older version on slave comparing to its master.

In any case your versions used are ages old. Please, upgrade to recent one, 5.1.59, starting with slave, then check if the problem still happens.
[26 Oct 2011 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[27 Oct 2011 4:44] Anil Alpati
Clarified the issue. Hence closing the ticket