error in mysql restart after dropped and created partitioned table

keydbas

I have dropped partitioned table and then created again with another partition key

as it is dropped but still in restart it shows earlier partiions' ibd files which no exists any more

200304  8:05:05  InnoDB: Error: trying to open a table, but could not

InnoDB: open the tablespace file './labrules/file_rule_hit_log#P#[email protected]@002d2018.ibd'!

InnoDB: Have you moved InnoDB .ibd files around without using the

InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?

InnoDB: It is also possible that this is a temporary table #sql...,

InnoDB: and MySQL removed the .ibd file for this.

InnoDB: Please refer to

InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html

InnoDB: for how to resolve the issue.

200304  8:05:05  InnoDB: Operating system error number 2 in a file operation.

InnoDB: The error means the system cannot find the path specified.

InnoDB: If you are installing InnoDB, remember that you must create

InnoDB: directories yourself, InnoDB does not create them.

200304  8:05:05  InnoDB: Error: trying to open a table, but could not

InnoDB: open the tablespace file './labrules/file_rule_hit_log#P#[email protected]@002d2019.ibd'!

InnoDB: Have you moved InnoDB .ibd files around without using the

InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?

InnoDB: It is also possible that this is a temporary table #sql...,

InnoDB: and MySQL removed the .ibd file for this.

InnoDB: Please refer to

InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html

InnoDB: for how to resolve the issue.

200304  8:05:05  InnoDB: Operating system error number 2 in a file operation.

InnoDB: The error means the system cannot find the path specified.

InnoDB: If you are installing InnoDB, remember that you must create

InnoDB: directories yourself, InnoDB does not create them.

200304  8:05:05  InnoDB: Error: trying to open a table, but could not

InnoDB: open the tablespace file './labrules/file_rule_hit_log#P#UPPER_CATCHALL.ibd'!

InnoDB: Have you moved InnoDB .ibd files around without using the

InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?

InnoDB: It is also possible that this is a temporary table #sql...,

InnoDB: and MySQL removed the .ibd file for this.