Re: replication from 4.1 to 5.5 and character set change
Hi, and thanks for the quick reply.
As you said, blob type has no character, because it is a binary.
The problem is:
we need to convert an entire db from latin to utf8, but we can not made downtime.
We should be able to do all using the replica ...
I don't know if anyone made this type of changes ...
Our application are just tested on mysql 5.5, but the problem are the blob field.
Reading on some forums, someone suggest to change the blob field into a text, convert the text, and then come back to blob ... every change is done on a slave.
I mean:
5.0 ( iso - blob ) -> 5.1 ( iso - text ) -> 5.1 ( utf8 - text ) -> 5.1 ( utf8 - blob ) -> 5.5 ( utf8 - blob )
Ideally this complex replica should work... but the replica stop on the 2* replica ( 5.1 ( utf8 - text ) ) with the error: Incorrect string value: '\xE9*^"\xA3$ ....
I tried to change the bin-log format replication from statemnet to row, but in this case i receive the error: cannot be converted from type 'varchar(255)' to type 'varchar(255)', Error_code: 1677
I have no other idea ....
could someone help us in this particular activity?
Thanks
Gaspare
Subject
Views
Written By
Posted
4814
February 10, 2012 09:42AM
2309
February 11, 2012 01:40PM
Re: replication from 4.1 to 5.5 and character set change
3659
February 14, 2012 10:26AM
2461
February 17, 2012 10:15PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.