Can't Delete Orphaned MySQL Temp Table
Since it is a temp table, you are OK to just delete the files.

rm -f *#sql-ib32694.*


Is this harmful to InnoDB ? No. There was a data dictionary entry still inside ibdata1. However, that entry is either missing or invalid (due to the tablespace_id). There is actually a one in 1,099,511,627,766 chance of it causing a problem.

See my older posts on why it is not that harmful and how to deal with


Jun 04, 2014 : temp table (#sql-7a87_230c32.ibd along with its .frm) still exists on slave
Dec 23, 2014 : #1025 - Error on rename of table errno: 150 : Table was deleted while tried to assign foreign key


Please keep in mind that temp tables (regardless of storage engine) are transient in nature. A temp table will disappear under these circumstances:


When a query is finished using it
When a DB connection terminates normally
When a DB connection terminates abnormally


If a temp table still exists due to a crash, rest assured that the data dictionary no longer acknowledges its existence. Please delete them and keep a good conscience.

If you are worried about, your only recourse when this happens is to perform a fully InnoDB Cleanup. See my post Howto: Clean a mysql InnoDB storage engine? in StackOverflow. The lesson here


Use CREATE TEMPORARY TABLE (...) ENGINE=MyISAM; if you have to use temp tables in your app.
Any system-generated InnoDB temp tables can be deleted after a crash.