从mysql.err文件中看到一下内容:
120224 8:13:46 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex此处一大串数字
786;InnoDB: End of page dump
120224 8:13:46 InnoDB: Page checksum 2947841960, prior-to-4.0.14-form checksum 1077062177
InnoDB: stored checksum 1948262432, prior-to-4.0.14-form stored checksum 168364320
InnoDB: Page lsn 1752134516 544173600, low 4 bytes of lsn at page end 540489782
InnoDB: Page number (if stored to page already) 538997359,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 541683305
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 15598.
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 InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120224 8:14:46 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Last MySQL binlog file position 0 3731577, file name .\log.000180但是不知道是什么意思,我想看看日志当中这个时间点到底是执行了什么语句产生的,但是mysql.log文件太大了,无法打开啊,怎么办?
120224 8:13:46 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex此处一大串数字
786;InnoDB: End of page dump
120224 8:13:46 InnoDB: Page checksum 2947841960, prior-to-4.0.14-form checksum 1077062177
InnoDB: stored checksum 1948262432, prior-to-4.0.14-form stored checksum 168364320
InnoDB: Page lsn 1752134516 544173600, low 4 bytes of lsn at page end 540489782
InnoDB: Page number (if stored to page already) 538997359,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 541683305
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 15598.
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 InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120224 8:14:46 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Last MySQL binlog file position 0 3731577, file name .\log.000180但是不知道是什么意思,我想看看日志当中这个时间点到底是执行了什么语句产生的,但是mysql.log文件太大了,无法打开啊,怎么办?
解决方案 »
- 关于mysql 5.5.30的安装问题
- 我是新人,想学mysql,求让我分享一下各位大神学习mysql的过程
- ERROR 1336 (0A000): Dynamic SQL is not allowed in stored function or trigger
- mysql中是否有办法知道数据表被修改过?
- mysql数据库 enum类型问题
- mysql的数据库迁移问题!
- 关于mysql与PHP链接的问题,急
- MYSQL ERROR:Can't get stat of 'C:\Program Files\Borland\CBuilder6\Projects\DBclient\Book1.csv'
- 请问mysql存储的if这样写对吗
- 如何求匹配次数在一个字段中匹配多少次
- 高手来帮忙看一下
- 有个问题向高手请教,在线等
INNODB的文件损坏。想办法找到以前的备份恢复一下试试。