MySQL服务启动时，错误：1067，进程意外终止

内容导读

互联网集市收集整理的这篇技术教程文章主要介绍了MySQL服务启动时，错误：1067，进程意外终止，小编现在分享给大家，供广大互联网技能从业者学习和参考。文章包含3568字，纯文字阅读大概需要6分钟。

内容图文

寻找错误日志，日志默认在： C:\ProgramData\MySQL\MySQL Server 5.6\data\LI-PC.err 错误日志如下： InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.ibdInnoDB: We do not continue the crash recovery, because

寻找错误日志，日志默认在：
C:\ProgramData\MySQL\MySQL Server 5.6\data\LI-PC.err
错误日志如下：

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.
140424  9:34:06 [Note] Plugin 'FEDERATED' is disabled.
140424  9:34:06 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
140424  9:34:06 InnoDB: The InnoDB memory heap is disabled
140424  9:34:06 InnoDB: Mutexes and rw_locks use Windows interlocked functions
140424  9:34:06 InnoDB: Compressed tables use zlib 1.2.3
140424  9:34:06 InnoDB: CPU does not support crc32 instructions
140424  9:34:06 InnoDB: Initializing buffer pool, size = 49.0M
140424  9:34:06 InnoDB: Completed initialization of buffer pool
140424  9:34:06 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140424  9:34:06  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
140424  9:34:06 [ERROR] InnoDB:  InnoDB: Error: Attempt to open a tablespace previously opened.
Previous tablespace hibernate/teacher uses space ID: 2 at filepath: .\hibernate\teacher.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.

解决方案：仅从上述信息看，是innodb 的数据文件损坏，在我安装Mysql的数据目录：C:\ProgramData\MySQL\MySQL Server 5.6\data下,一般来说，直接删除ibdata1, ib_logfile0, .. 等innodb的文件，让MYSQL自动重建即可。

内容总结

以上是互联网集市为您收集整理的MySQL服务启动时，错误：1067，进程意外终止全部内容，希望文章能够帮你解决MySQL服务启动时，错误：1067，进程意外终止所遇到的程序开发问题。 如果觉得互联网集市技术教程内容还不错，欢迎将互联网集市网站推荐给程序员好友。

内容备注

版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请发送邮件至 gblab@vip.qq.com 举报，一经查实，本站将立刻删除。

内容手机端