客户生产环境MySQL 5.6.47服务器的表无法访问，报错InnoDB: Database page corruption on disk or a failed

客户名称: 保密

数据类型: MySQL 5.6.47 on Windows

数据库大小: 288 MB

故障检测: MySQL错误日志文件显示:

InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 2588.
InnoDB: You may have to recover from a backup.

2024-02-19 21:50:16 40b0 InnoDB: uncompressed page, stored checksum in field1 3194719774, calculated checksums for field1: crc32 2896992689, innodb 4013046878, none 3735928559, stored checksum in field2 977073397, calculated checksums for field2: crc32 2896992689, innodb 977073397, none 140702569578223, page LSN 242 3535293243, low 4 bytes of LSN at page end 3535293243, page number (if stored to page already) 2588, space id (if created with >= MySQL-4.1.1 and stored already) 4334
InnoDB: Page may be an index page where index id is 4738
InnoDB: (index "PRIMARY" of table "70characters"."item_instance")
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 2588.
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 2588.
InnoDB: You may have to recover from a backup.

使用北京雨翰数据恢复研发的MySQL数据库恢复工具从损坏的表的数据文件item_instance.ibd恢复所有数据。

恢复出来的重要业务表的数据预览：

修复结果: 数据恢复率达100% 客户非常满意。将恢复出来的重要业务表的数据导入客户生产环境使用没有任何问题。