文档章节

mysql 无法启动

qii
 qii
发布于 2016/07/01 10:12
字数 488
阅读 76
收藏 0

错误信息

2016-07-01  9:37:56 2664 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-07-01  9:37:56 2664 [Note] InnoDB: The InnoDB memory heap is disabled
2016-07-01  9:37:56 2664 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-07-01  9:37:56 2664 [Note] InnoDB: Memory barrier is not used
2016-07-01  9:37:56 2664 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-07-01  9:37:57 2664 [Note] InnoDB: Not using CPU crc32 instructions
2016-07-01  9:37:57 2664 [Note] InnoDB: Initializing buffer pool, size = 64.0M
2016-07-01  9:37:57 2664 [Note] InnoDB: Completed initialization of buffer pool
2016-07-01  9:37:57 2664 [Note] InnoDB: Highest supported file format is Barracuda.
2016-07-01  9:37:57 2664 [Note] InnoDB: The log sequence numbers 37077739 and 37077739 in ibdata files do not match the log sequence number 37077749 in the ib_logfiles!
2016-07-01  9:37:57 2664 [Note] InnoDB: Database was not shutdown normally!
2016-07-01  9:37:57 2664 [Note] InnoDB: Starting crash recovery.
2016-07-01  9:37:57 2664 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-07-01  9:38:11 2664 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace tp5/qii_menu uses space ID: 21 at filepath: .\tp5\qii_menu.ibd. Cannot open tablespace ymtx/az_brand which uses space ID: 21 at filepath: .\ymtx\az_brand.ibd
InnoDB: Error: could not open single-table tablespace file .\ymtx\az_brand.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.

看最后一句,在my.ini里面设置innodb_force_recovery>0试试

innodb_force_recovery=1

重启mysql,搞定了。

 

but,问题又来了。

insert数据,没有问题。但是update,就不行了。

1036:table xx is read only.

打开日志一看。

innodb Started in read only mode

wtf.

翻到一篇帖子:

http://stackoverflow.com/questions/25394466/my-sql-error-1015-cant-lock-file-errno-165-table-is-read-only-innodb-en

把刚才加的那句配置,删掉,重启,ok。

© 著作权归作者所有

共有 人打赏支持
下一篇: go chan
qii

qii

粉丝 13
博文 77
码字总数 23520
作品 0
昆明
高级程序员
私信 提问

暂无文章

没什么启示的启示——《中国生存启示录》读后感4300字范文

没什么启示的启示——《中国生存启示录》读后感4300字范文: 文:夜晨1981。先后两次阅读这本书,第一次是2016年3月,第二次是2018年12月。读了两遍,都有一个理由,就是梁晓声这个名字。不知...

原创小博客
昨天
3
0
ubuntu常用操作

显卡GPU 查看显卡信息sudo lshw -numeric -class video# 查看显卡型号lspci | grep -i nvidia# 查看驱动版本sudo dpkg --list | grep nvidia-*或者 ubuntu-drivers devices#查看显卡...

hc321
昨天
2
0
mysql密码重置

方法一: 在my.ini的[mysqld]字段加入: skip-grant-tables 重启mysql服务,这时的mysql不需要密码即可登录数据库 然后进入mysql mysql>use mysql; mysql>更新 update user set password=pas...

architect刘源源
昨天
6
1
SpringBoot + Mybatis 配置多数据源(Srping boot 二)

前置条件,你已经配置好spring boot+mybatis,可以参考之前的博客 实现逻辑通过注解+aop切面编程来动态更新datasource 第一步,配置多个DataSource server: port: 8080freezing: ...

小海bug
昨天
13
0
连续潜在变量---概率PCA

最大似然PCA 用于PCA的EM算法 贝叶斯PCA 因子分解

中国龙-扬科
昨天
6
0

没有更多内容

加载失败,请刷新页面

加载更多

返回顶部
顶部