Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

problems restoring a  version 3.23.49 MYSQLDUMP to version 5.0.45 MySQL server

Posted on 2007-11-27
3
Medium Priority
?
954 Views
Last Modified: 2011-10-03
Hello Experts,

I need to move a MySQL database that is currently residing on a Linux server onto Windows server. The Linux server is running MySQL server version 3.23.49 and the OS is a flavour of Red Hat. The Windows server is Windows 2003 and is running version 5.0.45 of MySQL.

On the linux box I ran the following command :-

mysqldump -a -A -u root --password=manti156 www_website_apps_dev > apps_dev.sql

On the Windows box I ran the following command :-

mysql -u root --password=****** www_website_apps_dev < apps_dev.sql

which is giving the following error....

C:\Program Files\MySQL\MySQL Server 5.0\bin>mysql -u root --password=****
www_website_apps_dev < apps_dev.sql
ERROR 1064 (42000) at line 9201: You have an error in your SQL syntax; check the
 manual that corresponds to your MySQL server version for the right syntax to us
e near '-is_active-publication_date-start_date (id,is_active)
) TYPE=MyISAM' at line 23

Can anyone help ?




problems restoring a  version 3.23.49 MYSQLDUMP from to version 5.0.45 MySQL server
0
Comment
Question by:Oxfam_Australia
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 19

Expert Comment

by:Kim Ryan
ID: 20363168
Can you show the SQL statements at line 9201. There is probably something there that shows why the SQL syntax is not compatible. When upgrading from 3.23 the reference manuals suggest going to 4.0 first and then to 5.0. But you may be able to alter the SQL dump statements directly to solve the problem
0
 

Author Comment

by:Oxfam_Australia
ID: 20363332
These are the lines that make up the create :-

CREATE TABLE mm_article (

  id int(11) NOT NULL auto_increment,

  title varchar(255) NOT NULL default '',

  byline varchar(255) NOT NULL default '',

  description text NOT NULL,

  content text NOT NULL,

  author_id int(11) NOT NULL default '0',

  publication_date int(11) NOT NULL default '0',

  creation_date timestamp(14) NOT NULL,

  start_date int(11) NOT NULL default '0',

  end_date datetime default '0000-00-00 00:00:00',

  external_url varchar(100) NOT NULL default '',

  external_link_in_title tinyint(1) NOT NULL default '0',

  is_active tinyint(1) NOT NULL default '0',

  edit_admin_id int(11) NOT NULL default '0',

  edit_date int(11) NOT NULL default '0',

  publication_date3 date default '0000-00-00',

  start_date3 datetime default '0000-00-00 00:00:00',

  last_edited_by tinytext NOT NULL,

  edit_ipaddress int(11) NOT NULL default '0',

  PRIMARY KEY  (id),

  FULLTEXT KEY full_text (title,description,byline,content),

  KEY id-is_active-publication_date-start_date (id,is_active)

) TYPE=MyISAM;


The offending line is :-

KEY id-is_active-publication_date-start_date (id,is_active)

Do you think I could simple remove this line ?

Thanks,
0
 
LVL 19

Accepted Solution

by:
Kim Ryan earned 1500 total points
ID: 20363616
This line doesn't look right
FULLTEXT KEY full_text (title,description,byline,content),
From my manuals, there can only be FULLTEXT INDEX, sio I would try changing it to that first.

As a work around, you could remove the lines with keys and indexes in them and then create the index once the data is imported.
0

Featured Post

Learn how to optimize MySQL for your business need

With the increasing importance of apps & networks in both business & personal interconnections, perfor. has become one of the key metrics of successful communication. This ebook is a hands-on business-case-driven guide to understanding MySQL query parameter tuning & database perf

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this series, we will discuss common questions received as a database Solutions Engineer at Percona. In this role, we speak with a wide array of MySQL and MongoDB users responsible for both extremely large and complex environments to smaller singl…
By, Vadim Tkachenko. In this article we’ll look at ClickHouse on its one year anniversary.
In this video, Percona Solution Engineer Dimitri Vanoverbeke discusses why you want to use at least three nodes in a database cluster. To discuss how Percona Consulting can help with your design and architecture needs for your database and infras…
In this video, Percona Solutions Engineer Barrett Chambers discusses some of the basic syntax differences between MySQL and MongoDB. To learn more check out our webinar on MongoDB administration for MySQL DBA: https://www.percona.com/resources/we…
Suggested Courses

722 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question