Re: Migrate 4.0.14 data to 5.1.30
According to another developer, Migration Toolkit is meant to
be used on 5.0.? and up. Not 4.0.? and up. See Bug 42479.
So, how did I migrate?
1) I used MYSQLDUMP to unload the databases. I did them separately because of size.
mysqldump --opt --user=username --password=password databasename
> [c:\...]dumpfilename.sql
This offloads table definitions and data.
2) Edit the offloaded file. I used MSWord because of the file sizes.
In the first few lines, mysqldump puts a line of solid dashes. This is diagnosed as an error in the next step and causes termination of the re-load.
On the line of dashes, add a space after the first two. This causes the line to be correctly processed as a comment in the next step.
3) After using Create Database databasename, run the following to define the tables and load the data.
mysql databasename -u username -p < [c:\...]dumpfilename.sql
This will put all your data back into the new 5.1.30 db's.
Subject
Written By
Posted
February 03, 2009 03:21AM
Re: Migrate 4.0.14 data to 5.1.30
February 05, 2009 01:17PM
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.