Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 958
  • Last Modified:

problems restoring a version 3.23.49 MYSQLDUMP to version 5.0.45 MySQL server

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
Oxfam_Australia
Asked:
Oxfam_Australia
  • 2
1 Solution
 
Kim RyanIT ConsultantCommented:
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
 
Oxfam_AustraliaAuthor Commented:
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
 
Kim RyanIT ConsultantCommented:
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

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now