Bug #39866 Can't DROP DATABASE following mysqlhotcopy of InnoDB tables
Submitted: 5 Oct 2008 10:58 Modified: 6 Oct 2008 5:11
Reporter: Nimrod Priell Email Updates:
Status: Not a Bug Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version: Ver 5.0.32-Debian_7etch5-log OS:Linux ( 2.6.18-5-686 #1 SMP i686 GNU/Linux)
Assigned to: CPU Architecture:Any
Tags: drop database, innodb, mysqlhotcopy, unknown table

[5 Oct 2008 10:58] Nimrod Priell
I did a mysqlhotcopy of a database containing 7 InnoDB tables. I (now) know that you cannot use mysqlhotcopy on InnoDB. However, the database is created, and SHOW TABLES shows all 7 tables, but they cannot be DROPped, either via DROP TABLE or via DROP DATABASE because of "ERROR 1051 (42S02): Unknown table '<names of the tables'".

How to repeat:
Create a database with an InnoDB table; Mysqlhotcopy the database; Try to DROP DATABASE on the copy.

Suggested fix:
That's for you to decide.
[6 Oct 2008 5:11] Sveta Smirnova
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://dev.mysql.com/doc/ and the instructions on
how to report a bug at http://bugs.mysql.com/how-to-report.php

You probably could just remove directory with broken *.frm files