3 messages in com.mysql.lists.win32RE: I did a bad thing
FromSent OnAttachments
Anthony Johnston03 Jan 2002 02:27 
Heikki Tuuri03 Jan 2002 03:43 
Anthony Johnston03 Jan 2002 03:51 
Subject:RE: I did a bad thing
From:Anthony Johnston (an@antix.co.uk)
Date:01/03/2002 03:51:40 AM
List:com.mysql.lists.win32

ta, just the job, all fixed now

-----Original Message----- From: Heikki Tuuri [mailto:Heik@innodb.com] Sent: 03 January 2002 11:43 To: win@lists.mysql.com Subject: Re: I did a bad thing

Hi!

Look at section 15.1 of the manual http://www.innodb.com/ibman.html

Regards,

Heikki Innobase Oy

dropped a database using innodb table, without dropping the tables individually, now I cant recreate the tables in a database of the samename. Can anyone tell me how to sort this? All the best Ant. Anthony Johnston +44 (0) 7899 793 042 an@antix.co.ukAntix Software Limited http://www.antix.co.uk

15.1 Troubleshooting data dictionary operations A specific problem with tables is that MySQL keeps its own data dictionary information in .frm files it stores into the database directories, while InnoDB stores its own information into InnoDB's own data dictionary inside the data files. If you move .frm files around, or use DROP DATABASE in MySQL versions < 3.23.44, or the server crashes in the middle of a data dictionary operation, then the .frm files may end up to be out-of-sync with the InnoDB internal data dictionary.

A symptom of an out-of-sync data dictionary is that a CREATE TABLE statement fails. Then you should look into the error log. If it says that the table already exist inside the InnoDB internal data dictionary, then you have an orphaned table inside InnoDB data files, without a corresponding .frm file.

InnoDB: Error: table test/parent 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 moving the .frm file to the current database. InnoDB: Then MySQL thinks the table exists, and DROP TABLE will InnoDB: succeed. You can drop the orphaned table by following the above instructions in the error log.

--------------------------------------------------------------------- Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" before posting. To request this thread, e-mail win3@lists.mysql.com

To unsubscribe, send a message to the address shown in the List-Unsubscribe header of this message. If you cannot see it, e-mail win3@lists.mysql.com instead.