Re: Can't reload from dump file - Gleb Paharenko - com.mysql.lists.mysql

2 messages in com.mysql.lists.mysqlRe: Can't reload from dump file

From	Sent On	Attachments
Chris Mason (Lists)	29 Jan 2006 15:38
Gleb Paharenko	30 Jan 2006 05:01

Subject:	Re: Can't reload from dump file
From:	Gleb Paharenko (Gleb...@ensita.net)
Date:	01/30/2006 05:01:47 AM
List:	com.mysql.lists.mysql

Hello.

Perhaps, you haven't recreated the InnoDB tablespace after moving the database. Recreate the InnoDB table space, or follow recommendations from the error message. About InnoDB table space you can read here: http://dev.mysql.com/doc/refman/5.0/en/innodb-configuration.html

Chris Mason (Lists) wrote:

We have had some problems with corrupt data due to running out of space recently. I wanted to repair the tables so I backed up our database by dumping to a file with mysqldump. I then tried to repair the database and had some problems with that. I stopped MySQL and moved the database to database.old and restarted the database. I wanted to import the dump file. As it is 700 MB it takes a while to load. I got this error

[root@server8 backups]# mysql -u root -p<rt3.sql Enter password: ERROR 1005 (HY000) at line 694: Can't create table './rt3/Attributes.frm' (errno: 121)

and in the error file:

060129 19:27:32 InnoDB: Error: table `rt3/Attributes` already exists in InnoDB internal InnoDB: data dictionary. Have you deleted the .frm file InnoDB: and not used DROP TABLE? Have you used DROP DATABASE InnoDB: for InnoDB tables in MySQL version <= 3.23.43? InnoDB: See the Restrictions section of the InnoDB manual. InnoDB: You can drop the orphaned table inside InnoDB by InnoDB: creating an InnoDB table with the same name in another InnoDB: database and copying the .frm file to the current database. InnoDB: Then MySQL thinks the table exists, and DROP TABLE will InnoDB: succeed. InnoDB: You can look for further help from InnoDB: http://dev.mysql.com/doc/mysql/en/InnoDB_troubleshooting_datadict.html

What can I do?