So I successfully upgraded a test db server from 5.0.96 all the way up to 5.6
Replication as the slave, where the master is 5.0.96, started working
for about 10 minutes and then got the following error:
[ERROR] Slave SQL: Error 'Duplicate entry 'data' for key 'PRIMARY'' on
query. Default database
going form 5.1 - to 5.5 was easy, I did not have to dump any tabels or
triggers, just upgraded binary, ran mysql_upgrade and worked in no
time.
Thanks everyone for the help!
On Wed, Feb 20, 2013 at 2:33 PM, Reindl Harald wrote:
> fine and much faster and probably safer too :-)
>
> a backup with
fine and much faster and probably safer too :-)
a backup with rsync is faster as dump/import and
can be done with minimize downtime by use it
twice, the first time hot-backup with running
server and the second time after stop server
to get the diffs
doing rsync -> stop -> rsync -> start in a scri
This is on a slave, i only upgraded on one box which is the slave i
have not touched master
On Wed, Feb 20, 2013 at 5:41 PM, Reindl Harald wrote:
>
>
> Am 20.02.2013 23:27, schrieb Mike Franon:
>> So I successfully upgraded a test db server from 5.0.96 all the way up to 5.6
>>
>> Replication as t
Hello,
FYI, I found this statement in the doc, at the end of the C API main page:
http://dev.mysql.com/doc/refman/5.6/en/c.html
If, after an upgrade, you experience problems with compiled client programs, such as Commands out of sync or unexpected core dumps, you probably have
used old header
Am 20.02.2013 23:27, schrieb Mike Franon:
> So I successfully upgraded a test db server from 5.0.96 all the way up to 5.6
>
> Replication as the slave, where the master is 5.0.96, started working
> for about 10 minutes and then got the following error:
>
> [ERROR] Slave SQL: Error 'Duplicate en
OK I got it to work.
I dumped the tables that it was complaining about first, and then
dumped the triggers.
I then uninstalled anything to do with mysql, and installed 5.1
Then imported the tables and triggers, and and able to run
mysql_upgrade without any errors.
This is all without using a fu
I am pretty sure I did, and when I did I got the following errors:
Error: Table Upgrade Required, Please dump/reload to fix it
I got that on 10 tables, and also got the following:
Warning: Triggers for table ' have no creation context.
I think it has to do with no triggers.
I know hen I ra
So I did a full mysqldump over the weekend for a second time and this
time it is 220GB, no clue what happened last time, I should have
realized looking at the file size something was wrong, but since I got
no errors did not think about it, and this time I timed it, took 7
hours to do a complete mys
Am 20.02.2013 18:26, schrieb Mike Franon:
> So I did a full mysqldump over the weekend for a second time and this
> time it is 220GB, no clue what happened last time, I should have
> realized looking at the file size something was wrong, but since I got
> no errors did not think about it, and thi
10 matches
Mail list logo
