mysql日常错误信息解决方法:InnoDB: and force InnoDB to continue crash recovery here.
时间：2014-05-09 12:50:46
收藏：0
阅读：1089
今天早上上班来打开环境，mysql报了这个错误，猜到的原因应该是昨天晚上下班没等mysql服务器退出就关闭计算机。
|
1
2
3
4
5
6
7
8
9
10
11
12
13 |
2014-05-09
09:44:25
4128 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace manage_yunfan/nav_areasource uses space ID: 2
at filepath: .\manage_yunfan\nav_areasource.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2
at filepath: .\mysql\innodb_index_stats.ibdInnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.ibdInnoDB: We do
not continue
the crash recovery, because the table may becomeInnoDB: 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 cannotInnoDB: 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 normalInnoDB: crash recovery and ignore that table.InnoDB: 3) If the file system or the disk is broken, and you cannot removeInnoDB: the .ibd file, you can set innodb_force_recovery > 0
in my.cnfInnoDB: and force InnoDB to continue
crash recovery here. |
解决方法：修改mysql.ini
PS:其实错误日志已经告诉我们该怎么做了：InnoDB: the .ibd file, you can set
innodb_force_recovery > 0 in my.cnf
这句话的意思是让我们增加一条配置 设置此innodb_force_recovery >
0，所以我尝试设置为1，然后重启成功。
# The MySQL server
[mysqld]
innodb_force_recovery = 1
/*增加一行，让其独立运行，注意一定要是在mysqld选项下*/
mysql日常错误信息解决方法:InnoDB: and force InnoDB to continue crash recovery here.,布布扣,bubuko.com
评论（0）