4.1 to 5.0 migration - key error
I have a couple of databases on a system running MySQL 4.1.20 that I need to load on a system running 5.0.51a. I performed a routing mysqldump, copied over the sql file and attempted a read. I got the infamous "key was too long" error. Everything I've read about this error was related to 4.0 databases being latin1 encoded. However, this 4.1 database appears to be utf8 already.
/*!40101 SET NAMES utf8 */;
Can someone point me to some instructions on how to dump a 4.1 database and restore it to a 5.0 system?
I suspect this is an FAQ, but couldn't track down a good example.
Sakshale
PS - My desktop is OS X, so the migration tool isn't available. The target server is a Linux box, but I can't run a GUI on it... sigh.
Subject
Written By
Posted
4.1 to 5.0 migration - key error
December 01, 2008 07:30PM
December 02, 2008 07:01PM
December 06, 2008 02: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.