日期:2014-05-16  浏览次数:20863 次

高分求助 mysql 启动1067错误 qq 25258767
ibdata1 文件和 frm 文件都在 ,新建个空的mysql 环境, 这两个文件都替换然后启动还是不行,郁闷了啊!
错误日志如下 
111012 18:19:26 InnoDB: Page checksum 2152224473, prior-to-4.0.14-form checksum 2744295034
InnoDB: stored checksum 33203219, prior-to-4.0.14-form stored checksum 240
InnoDB: Page lsn 2701852676 3127509335, low 4 bytes of lsn at page end 184611355
InnoDB: Page number (if stored to page already) 1048576,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 352367159
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 8296.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
111012 18:19:26 - mysqld got exception 0xc0000005 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.


------解决方案--------------------
既然是空环境为什么要替换这两个文件呢?

如果想迁移数据:
把 ib_logdata* 文件删除了,再重启试试。
再不行试试配置文件中配置 innodb_force_recovery 4 重启?
再不行,你就在原库里dump出来再导入呗。
------解决方案--------------------
"既然是空环境为什么要替换这两个文件呢?"

+1,不用dump而要换文件,你图个啥?
------解决方案--------------------
INNODB是不能直接COPY的,要用MYSQLDUMP备份后再导入
------解决方案--------------------
删除你的这几个文件,然后再重启试试。ibdata1
ib_logfile0
ib_logfile1

做好备份。
------解决方案--------------------
探讨
删除你的这几个文件,然后再重启试试。ibdata1
ib_logfile0
ib_logfile1

做好备份。