history_uint損壞使mysql重啟頻繁最后導致zabbix_server關閉該怎么辦

本文主要給大家簡單講講history_uint損壞使mysql重啟頻繁最后導致zabbix_server關閉該怎么辦，相關專業術語大家可以上網查查或者找一些相關書籍補充一下，這里就不涉獵了，我們就直奔主題吧，希望history_uint損壞使mysql重啟頻繁最后導致zabbix_server關閉該怎么辦這篇文章可以給大家帶來一些實際幫助。

問題：13:15:47  InnoDB: Page checksum 2390903969, prior-to-4.0.14-form checksum 2524550738

InnoDB: stored checksum 2319722401, prior-to-4.0.14-form stored checksum 192332111

InnoDB: Page lsn 0 1902263731, low 4 bytes of lsn at page end 1900395394

InnoDB: Page number (if stored to page already) 16222,

InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0

InnoDB: Page may be an index page where index id is 0 462

InnoDB: (index "GEN_CLUST_INDEX" of table "zabbix"."history_uint")

InnoDB: Database page corruption on disk or a failed

InnoDB: file read of page 16222.

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

解決方法：

在my.cnf中添加innodb_force_recovery=1 ，并重啟mysql

[root@zabbix /]# /etc/init.d/mysqld restart

新建同結構表，引擎為myisam

mysql> use zabbix

mysql> create table history_uint_new like history_uint; 

mysql> alter table history_uint_new type=myisam;

將原表數據導入到新建的表中；

mysql> Insert into history_uint_new select * from history_uint;

mysql> exit

在my.cnf中注釋掉innodb_force_recovery=1 ，并重啟mysql

[root@strongzabbix /]# /etc/init.d/mysqld restart

修改新表引擎為innodb

mysql> use zabbix

Alter table history_uint_new type=innodb; 

刪除原表

mysql> Drop table history_uint; 

將新表名稱改為原表并刷新權限，重啟mysql

mysql> rename table history_uint_new to history_uint;  

mysql> flush privileges; 

mysql> exit

[root@strongzabbix /]# /etc/init.d/mysqld restart

history_uint損壞使mysql重啟頻繁最后導致zabbix_server關閉該怎么辦就先給大家講到這里，對于其它相關問題大家想要了解的可以持續關注我們的行業資訊。我們的板塊內容每天都會捕捉一些行業新聞及專業知識分享給大家的。