错误InnoDB:Attemptedtoopenapreviouslyopenedtablespace.
2013-10-19 03:29
501 查看
2013-08-04 13:48:22 760 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace isaactest/wp_usermeta uses
space ID: 2 at filepath: .\isaactest\wp_usermeta.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.
出现这个问题好几次了,每次的解决问题都是重新弄下Mysql.
我用的是XAMPP 1.83,今天终于找到解决办法了
在D:\xampp\mysql\bin下面的my.ini中添加
innodb_force_recovery = 1
OK,谢谢。
space ID: 2 at filepath: .\isaactest\wp_usermeta.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.
出现这个问题好几次了,每次的解决问题都是重新弄下Mysql.
我用的是XAMPP 1.83,今天终于找到解决办法了
在D:\xampp\mysql\bin下面的my.ini中添加
innodb_force_recovery = 1
OK,谢谢。
相关文章推荐
- 【Roger】linux下PCI9054驱…
- linux下配置IP地址
- SOA架构师 职责 HP SH
- 下载开源CentOS的几个国内镜像站点
- 选择安防监控系统镜头时需注意各种…
- 无法创建普通文件"/mnt/floppy/loader.bin": 设备上没有空间
- linux(本机)配置域名(多域名)
- linux 系统tty、pty和pts 的概念及区别
- Nginx初探之安装
- linux命令小记
- Linux 下 SQL*Plus 上下键不能查看历史命令
- nginx+phpmyadmin
- centos 文件新建、删除、移动、复制等命令
- CentOS—device eth0 does not seem to be present,...
- OpenCart Ajax单页结账Ajax One Page Checkout
- OpenCart高级配送模块(OCC Shipping)
- OpenCart poll/vote在线投票插件
- OpenCart拖放式图片管理器
- linux学习 xinetd服务管理
- linux——fork(进程)