SantaMufasa
Technical User
I successfully created a dump file from a 4.0.12 database instance (on a Windows server) using this command:
I copied the resulting dump file over to another Windows server on which I have installed MySQL 5.0.45. On the new server, I created an empty database, naming it the same name as the source database on the 4.0.12 instance.
On the server with the 5.0.45 instance, I issued this restore command:
After chugging away (successfully) for several minutes, the restore process threw this error:
Since I cannot successfully edit this 771MB dump file (using any editor of which I am aware -- e.g. Notepad, Wordpad, Word, even "vi"), how can I see, troubleshoot, then fix, the full text of the offending code to make it 5.0.45 compliant?
Or, is there some method of my "pre-validating" a 4.0.12 dump file for use in 5.0.45?
Or, is there a better way to migrate large databases from 4.0.12 to 5.0.45?
Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]
Code:
mysqldump --opt -u<username> -p<password> -r<dump file name> <database name>
****************************************************************************
On the server with the 5.0.45 instance, I issued this restore command:
Code:
mysql -u<username> -p<password> <database name> < <dump file name>
Code:
ERROR 1064 (42000) at line 7847: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near
'condition varchar(240) default NULL,
report_style_id int(11) NOT NULL default '
at line 4
Or, is there some method of my "pre-validating" a 4.0.12 dump file for use in 5.0.45?
Or, is there a better way to migrate large databases from 4.0.12 to 5.0.45?
Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]