MySQL服务启动时,错误:1067,进程意外终止
来源:互联网 发布:java 带文件表单提交 编辑:程序博客网 时间:2024/05/18 00:55
寻找错误日志,日志默认在:
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 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.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 disabled140424 9:34:06 InnoDB: Mutexes and rw_locks use Windows interlocked functions140424 9:34:06 InnoDB: Compressed tables use zlib 1.2.3140424 9:34:06 InnoDB: CPU does not support crc32 instructions140424 9:34:06 InnoDB: Initializing buffer pool, size = 49.0M140424 9:34:06 InnoDB: Completed initialization of buffer pool140424 9:34:06 InnoDB: highest supported file format is Barracuda.InnoDB: The log sequence number in ibdata files does not matchInnoDB: 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.ibdCannot 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.
解决方案:仅从上述信息看,是innodb 的数据文件损坏,在我安装Mysql的数据目录:C:\ProgramData\MySQL\MySQL Server 5.6\data下,一般来说,直接删除ibdata1, ib_logfile0, .. 等innodb的文件,让MYSQL自动重建即可。
0 0
- MySQL服务启动时,错误:1067,进程意外终止
- MySql启动服务时:错误1067进程意外终止
- MySQL 服务无法启动 1067 错误 进程意外终止解决方法
- 无法启动MYSQL服务错误1067 进程意外终止
- 无法启动mysql服务,错误提示 1067:进程意外终止
- 计算机无法启动MYSQL服务错误1067进程意外终止
- 计算机无法启动mysql服务 1067 错误 ,进程意外终止
- MYSQL服务错误1067进程意外终止
- mysql启动错误1067:进程意外终止
- MySQL服务启动提示window无法启动MySQL服务 错误1067:进程意外终止
- mysql 启动时出现1067错误,进程意外终止。
- 成功解决 无法启动MySQL服务,错误1067:进程意外终止 错误
- Mysql 本地计算机无法启动 mysql 服务 错误 1067:进程意外终止
- MYSQL 无法启动MYSQL服务”1067 进程意外终止”解决办法
- mongoDB 服务无法启动 错误1067:进程意外终止
- Windows 无法启动MongoDB服务 错误1067:进程意外终止
- 本地无法启动MySQL服务,报的错误:1067,进程意外终止---解决
- 本地无法启动MySQL服务,报的错误:1067,进程意外终止
- 转换html代码子程序
- eclipse不自动编译
- 在Kali里安装VMware Tools
- 怎么把五子棋的单机版做成网络版?
- Quartz Job耗时太久问题
- MySQL服务启动时,错误:1067,进程意外终止
- ArcPy开发IDE
- Spring MVC 教程,快速入门,深入分析
- 内核分析网站
- 1 AndroidManifest.xml配置文件详解
- 关于Access数据库安全
- 澄清P问题、NP问题、NPC问题的概念
- ADODB.Stream的属性和用法
- Ubuntu Fire Wall (ufw) 防火墙 设置