WAMP mysql 无法启动的解决方法
2013-11-26 19:20
316 查看
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 正常启动
通过查看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 Apache和mysql服务无法启动的终极解决方法!!!!!!
- wamp Apache和mysql服务无法启动的终极解决方法!!!!!!
- ubuntu下磁盘空间不足导致mysql无法启动的解决方法
- mysql-5.7.11-winx64中mysql.exe双击无法看到进程,CMD下3534错误,无法启动的解决方法
- mysql 5.7.17 安装教程 附MySQL服务无法启动的解决方法
- Macos Yosemite Xampp Mysql无法启动解决方法
- MySQL因配置过大内存导致无法启动的解决方法
- wamp安装以后无法连接mysql解决方法
- MySQL服务无法启动【错误代码1067】的解决方法
- 关于XAMPP 无法启动mysql的解决方法
- 碰到MySQL无法启动1067错误问题解决方法
- XAMPP 1.7.0中MySql无法启动解决方法
- MySQL中配置文件my.cnf因权限问题导致无法启动的解决方法
- 关于mysql-5.7.13-winx64服务无法启动的解决方法
- mysql-5.7.11-winx64中mysql.exe双击无法看到进程,CMD下3534错误,无法启动的解决方法
- 安装MySQL 5后无法启动(不能Start service)解决方法小结
- Win10下安装MySQL后,"mysql -uroot -p"无法启动mysql服务的解决方法。
- MySql重装或者重新配置数据库实例时遇到“本地计算机无法启动Mysql服务”错误的解决方法
- "mysql服务无法启动 服务没有报告任何错误"解决方法
- 安装MySQL 5后无法启动(不能Start service)解决方法小结