[glitch23]

Originally Posted by jdell

I have 3 separate zimbra servers, and all 3 had the same errors reported by zmdbintegrityreport. I think there is definitely an upgrade bug that the integrity check has revealed. After the repair table, zmdbintegrityreport is clean on all my servers.

Per this page: What to Do When zmdbintegrityreport Reports Errors - ZimbraWiki

All had error posted above. All are RHEL4. All were upgrades from 4.0 to 4.5. A full dump/restore was only performed on 1 of the 3 boxes. 2 boxes RHEL4 32-bit, 1 RHEL4 64-bit. All error tables showed version 9, after repair, version was 10.

To be safe, I shutdown all of zimbra, backed up, and then just started mysql to make the changes:

# su - zimbra
# zmcontrol stop
# mysql.server start
# mysql
mysql> use mysql;
mysql> REPAIR TABLE `help_category`;
mysql> REPAIR TABLE `help_keyword`;
mysql> REPAIR TABLE `help_topic`;
mysql> use zimbra;
mysql> REPAIR TABLE `config`;
mysql> REPAIR TABLE `mailbox_metadata`;
mysql> REPAIR TABLE `out_of_office`;
mysql> REPAIR TABLE `service_status`;
mysql> REPAIR TABLE `table_maintenance`;
mysql> REPAIR TABLE `volume`;
mysql> exit
# zmdbintegrityreport (should be clean now)
# mysql.server stop
# zmcontrol start

That indeed fixed the integrity report. BTW the install this happened on was originally a ZCS 3.x version.