mysql 错误
来源:互联网 发布:森海塞尔隔音效果 知乎 编辑:程序博客网 时间:2024/05/18 02:54
2014-08-11 23:07:01 6624 [Note] Plugin 'FEDERATED' is disabled.
2014-08-11 23:07:01 6624 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-11 23:07:01 6624 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-08-11 23:07:01 6624 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-08-11 23:07:01 6624 [Note] InnoDB: Not using CPU crc32 instructions
2014-08-11 23:07:01 6624 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-08-11 23:07:01 6624 [Note] InnoDB: Completed initialization of buffer pool
2014-08-11 23:07:01 6624 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-11 23:07:01 6624 [Note] InnoDB: The log sequence numbers 1626253 and 1626253 in ibdata files do not match the log sequence number 1718328 in the ib_logfiles!
2014-08-11 23:07:01 6624 [Note] InnoDB: Database was not shutdown normally!
2014-08-11 23:07:01 6624 [Note] InnoDB: Starting crash recovery.
2014-08-11 23:07:01 6624 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-08-11 23:07:01 6624 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace blog/jh_user uses space ID: 6 at filepath: .\blog\jh_user.ibd. Cannot open tablespace dcs/dcsmember which uses space ID: 6 at filepath: .\dcs\dcsmember.ibd
InnoDB: Error: could not open single-table tablespace file .\dcs\dcsmember.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.
2014-08-11 23:07:01 6624 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-11 23:07:01 6624 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-08-11 23:07:01 6624 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-08-11 23:07:01 6624 [Note] InnoDB: Not using CPU crc32 instructions
2014-08-11 23:07:01 6624 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-08-11 23:07:01 6624 [Note] InnoDB: Completed initialization of buffer pool
2014-08-11 23:07:01 6624 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-11 23:07:01 6624 [Note] InnoDB: The log sequence numbers 1626253 and 1626253 in ibdata files do not match the log sequence number 1718328 in the ib_logfiles!
2014-08-11 23:07:01 6624 [Note] InnoDB: Database was not shutdown normally!
2014-08-11 23:07:01 6624 [Note] InnoDB: Starting crash recovery.
2014-08-11 23:07:01 6624 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-08-11 23:07:01 6624 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace blog/jh_user uses space ID: 6 at filepath: .\blog\jh_user.ibd. Cannot open tablespace dcs/dcsmember which uses space ID: 6 at filepath: .\dcs\dcsmember.ibd
InnoDB: Error: could not open single-table tablespace file .\dcs\dcsmember.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.
在D:\xampp\mysql\bin下面的my.ini中添加
innodb_force_recovery = 1
0 0
- mysql 错误
- MYSQL 错误
- mysql 错误
- mysql 错误
- mysql 错误
- MySQL错误
- mysql 错误
- MySql 错误
- mysql错误
- mysql 错误
- mysql错误
- mysql错误
- MySql错误
- mysql启动错误 错误1067
- MySQL错误处理--1146错误
- 查看mysql错误日志定位mysql错误
- 查看mysql错误日志定位mysql错误 .
- Mysql中mysql 1366错误
- LeetCode-Unique Paths II
- 电脑的脉搏—时钟频率的来龙去脉
- java zxing 生成带图片的二维码
- HOJ 12893 Just Enough Space
- OpenWrt Web界面修改及功能实现实例说明
- mysql 错误
- el表达式
- Android项目打包成APK文件
- python工具 文件字符串替换
- WEB前端开发学习----6.CSS 和 JS 在html的使用方法
- 百度员工离职总结:如何做个好员工
- 写入安卓内核的代码
- 用java的IO流和集合创建一个存储指定文件列表示例
- 从内存模型角度来看C++多态实现机制