mysql在本地计算机无法启动mysql56服务

码拜

9年 ago

windows xp下面装了mysql5.6，用了一段时间都很正常。但昨天突然无法启动mysql56服务了，报错：“在本地计算机无法启动mysql56服务，错误1067 进程意外终止”。 mysql.ini配置也没发生更改过，替换初始的mysql.ini文件后也报一样的错。3306端口也没被占用。回忆了下，此前装了google chrome浏览器，装浏览器之前mysql都好好的，难道是和chrome有冲突？如果不卸载重装mysql，有没有什么方案可以解决此问题？
#1 5分	去数据目录找一下err日志打开看下多半能知道原因
#2 5分	具体的看一下错误日志文件。
#3	130111 15:55:17 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 .\sakila\actor.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.
#4 10分	完了估计是数据文件损坏了有备份就用备份还原没备份的话只能在配置文件里加这个innodb_force_recovery=4强制启动然后尽快导出能导出的数据吧
#6	如果将my.ini文件改名为my-default.ini里面配置的属性好像没起作用啊。遇到上面的问题在网上看到另一种方法：删除data目录下的ib_logfile0和ib_logfile1文件。我是按照这个方法弄好的
#8	这样处理有些表和表里的数据会有损坏的吧？

CodeBye 版权所有丨如未注明 , 均为原创丨本网站采用BY-NC-SA协议进行授权 , 转载请注明mysql在本地计算机无法启动mysql56服务！