WAMP mysql 无法启动的解决方法

WAMP mysql 无法启动,手动启动wampmysqld进程报1067的错误。

通过查看mysql log,发现

2013-11-26 19:04:11 5068 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace usernet/message uses space ID: 9 at filepath: .\usernet\message.ibd. Cannot open tablespace usernet/messages which uses space ID: 9 at filepath: .\usernet\messages.ibd
2013-11-26 19:04:11 13b4  InnoDB: Operating system error number 997 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
InnoDB: Error: could not open single-table tablespace file .\usernet\messages.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.

由于数据不重要,我选择删除 messages.ibd 

重启wamp server 正常启动

你可能感兴趣的:(WAMP mysql 无法启动的解决方法)