problems importing dump

57 views
Skip to first unread message

Dave

unread,
Jun 16, 2009, 12:49:13 PM6/16/09
to MyTTC
Hey All,

Thanks so much for all your hard work in providing this data. It's
awesome to be able to have access to this.

I have a quick question, I'm trying to import the SQL dump in to MySQL
5.0.32-Debian_7etch1-log and I'm getting the following error:


dsullivan@vps:~$ mysql -u root -p
Enter password:
mysql> CREATE DATABASE `ttcdata` DEFAULT CHARACTER SET utf8 COLLATE
utf8_unicode_ci;
Query OK, 1 row affected (0.00 sec)
mysql> Bye
dsullivan@vps:~$ mysql -u root -p -D ttcdata < myttc_2008-12-21.sql
Enter password:
ERROR 126 (HY000) at line 157: Incorrect key file for table './ttcdata/
shape_points.MYI'; try to repair it

Are there any additional options I need to specify? Thanks!

Kevin Branigan

unread,
Jun 16, 2009, 1:19:57 PM6/16/09
to MyTTC
Hmm.. unfortunately I don't think I can much help as I've never seen
that error

I generally go:
cat myttc_2008-12-21.sql | mysql -uroot -p ttcdata

google searching 'mysql error 126' seems to return various mysql
settings fixes, perhaps one of those help?
I suggest dropping the database and trying it again from a blank DB

when i create my database I don't set it to utf8 or anything - I just
leave it to whatever it decides:
CREATE DATABASE ttcdata;
is all that I run, i'm not even sure what the defaults are actually.

Let me know how it goes, I'm curious what the problem is

Dave

unread,
Jun 16, 2009, 1:28:03 PM6/16/09
to MyTTC
Thanks for the tips! I figured I'd ask here before googling, in case
someone had run in to a similar problem. I'm going to try upgrading
MySQL on my server first, perhaps its a bug in the version I'm
running. If not I'll have to google around...

Kieran Huggins

unread,
Jun 16, 2009, 1:32:21 PM6/16/09
to my...@googlegroups.com
Better yet:

gunzip -c myttc_2008-12-21.sql.gz | mysql -uroot -p ttcdata


Then you get to keep your .gz file intact, and skip that annoying
unzipping step :-)

Kevin Branigan

unread,
Jun 16, 2009, 2:06:15 PM6/16/09
to my...@googlegroups.com
i always remember to do that directly after forgetting to do that,
then I have to replace the file

Dave M. Sullivan

unread,
Jun 16, 2009, 2:42:53 PM6/16/09
to my...@googlegroups.com
Upgraded MySQL, still no luck. Seems like its specific to MyISAM, so,
on a limb, I decided to try using another engine:

dsullivan@vps:~$ sed -e 's/MyISAM/InnoDB/g' myttc_2008-12-21.sql >
myttc_innodb.sql
dsullivan@vps:~$ cat myttc_innodb.sql | mysql -u root -p ttcdata

DONE!
--
Dave Sullivan
da...@dave-sullivan.com
647-638-3738
Reply all
Reply to author
Forward
0 new messages