InnoDB: Attempted to open a previously opened tablespace. Previous tablespace xspcf

wamp重启的时候,mysql报错了,提示InnoDB: Attempted to open a previously opened tablespace. Previous tablespace xspcf
 
错误信息:
2017-04-01 09:52:37 5756 [Note] Plugin 'FEDERATED' is disabled.
2017-04-01 09:52:37 5756 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-04-01 09:52:37 5756 [Note] InnoDB: The InnoDB memory heap is disabled
2017-04-01 09:52:37 5756 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-04-01 09:52:37 5756 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-04-01 09:52:37 5756 [Note] InnoDB: Not using CPU crc32 instructions
2017-04-01 09:52:37 5756 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-04-01 09:52:37 5756 [Note] InnoDB: Completed initialization of buffer pool
2017-04-01 09:52:37 5756 [Note] InnoDB: Highest supported file format is Barracuda.
2017-04-01 09:52:37 5756 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1468862501
2017-04-01 09:52:37 5756 [Note] InnoDB: Database was not shutdown normally!
2017-04-01 09:52:37 5756 [Note] InnoDB: Starting crash recovery.
2017-04-01 09:52:37 5756 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-04-01 09:52:37 5756 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace xspcf_on/dw_interface_log uses space ID: 92 at filepath: .xspcf_ondw_interface_log.ibd. Cannot open tablespace yilvcheng3/cc_agent which uses space ID: 92 at filepath: .yilvcheng3cc_agent.ibd
InnoDB: Error: could not open single-table tablespace file .yilvcheng3cc_agent.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配置文件,在【mysqld】添加:
innodb_force_recovery = 1

0 个评论

要回复文章请先登录注册