无法启动Mysql服务,错误InnoDB: Attempted to open a previously opened tablespace.
2013-08-04 13:55
381 查看
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,谢谢。
过了2个小时才发现,把这个设置为1的时候,会影响insert,delete....还是改为0
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,谢谢。
过了2个小时才发现,把这个设置为1的时候,会影响insert,delete....还是改为0
相关文章推荐
- 无法启动Mysql服务,错误InnoDB: Attempted to open a previously opened tablespace. - IsaacZhang
- Mysql无法启动 InnoDB: Attempted to open a previously opened tablespace
- mysql错误InnoDB:Attemptedtoopenapreviouslyopenedtablespace.
- 错误InnoDB:Attemptedtoopenapreviouslyopenedtablespace.
- Mysql 启动遇到 The server quit without updating PID file (/[FAILED]l/mysql/data/021rjsh216086s.pid)和Attempted to open a previously opened tablespace
- Mac xampp mysql Attempted to open a previously opened tablespace
- 无法启动Mysql服务 could not open single-table tablespace file
- Mac 下MAMP Pro MySQL无法启动报 Error: could not open single-table tablespace file ./mysql/innodb_table_sta
- MYSQL服务无法启动:InnoDB: .\ibdata1 can't be opened in read-write mode
- 在本地计算机无法启动mysql服务 错误1067:进程意外中止 日志错误:MySQL: Can't create/write to file 'D:\\mysql\Data\admin.pid' (Errcode: 13)
- MYSQL服务无法启动:InnoDB: .\ibdata1 can't be opened in read-write mode
- XAMPP 启动mysql报错 InnoDB: Error: could not open single-table tablespace file……
- 计算机无法启动MYSQL服务错误1067进程意外终止
- Mysql 服务无法启动 服务没有报告任何错误
- MySql服务无法启动系统出错发生系统错误1067进程意外终止,另类原因
- MySql服务无法启动,发生系统错误1067,进程意外终止
- Mysql5.6启动报错, [ERROR] InnoDB: Could not find a valid tablespace file for 'pa
- mysql无法启动服务没有报告任何错误
- 无法启动mysql服务 错误1067:进程意外中止
- mysql安装步骤及遇到的MySQL 服务无法启动。 服务没有报告任何错误。 请键入 NET HELPMSG 3534 以获得更多的帮助。