Issues with database integrity check
 Article Information |
|---|
| This article applies to the following ZCS versions. |
When upgrading from ZCS 4.5.6 or earlier to ZCS 4.5.7 or later, the following error may appear during the upgrade:
Generating report Database errors found. /opt/zimbra/mysql/bin/mysqlcheck --defaults-file=/opt/zimbra/conf/my.cnf -S /opt/zimbra/db/mysql.sock -A -C -s -u root --password=NU9WALN1TK110NnZZL7bLBGrI5GLyhV --auto-repair mysql.help_category error : Table upgrade required. Please do "REPAIR TABLE `help_category`" to fix it! mysql.help_keyword error : Table upgrade required. Please do "REPAIR TABLE `help_keyword`" to fix it! mysql.help_topic error : Table upgrade required. Please do "REPAIR TABLE `help_topic`" to fix it! mysql.user error : Table upgrade required. Please do "REPAIR TABLE `user`" to fix it! zimbra.config error : Table upgrade required. Please do "REPAIR TABLE `config`" to fix it! zimbra.mailbox_metadata error : Table upgrade required. Please do "REPAIR TABLE `mailbox_metadata`" to fix it! zimbra.out_of_office error : Table upgrade required. Please do "REPAIR TABLE `out_of_office`" to fix it! zimbra.service_status error : Table upgrade required. Please do "REPAIR TABLE `service_status`" to fix it! zimbra.table_maintenance error : Table upgrade required. Please do "REPAIR TABLE `table_maintenance`" to fix it! zimbra.volume error : Table upgrade required. Please do "REPAIR TABLE `volume`" to fix it!
zmdbintegrityreport is introduced in ZCS 4.5.6. It uses mysqlcheck to check for mysql db corruption.
Starting with 4.5.7, the upgrade script calls zmdbintegrityreport, and displays any errors that it may find.
Please DO NOT stop the upgrade due to this error because after displaying the errors, the install script will run "mysql_upgrade" with the correct parameters to fix the issue.
After the upgrade you can then run "/opt/zimbra/libexec/zmdbintegrityreport" again to verify that there's really no more error.
You don't need to repair the tables manually prior to the upgrade.
The zmdbintegrityreport errors were caused by bug [19008] http://bugzilla.zimbra.com/show_bug.cgi?id=19008, which has been fixed in 4.5.7.
Please also note that repair table does not work on innodb tables.
