zmdbintegrityreport errors after 4.5.7 upgrade

[jdell]

I upgraded our RHEL4 X86_64 server to 4.5.7 NE this weekend, and was greeted with a huge error list this morning. I upgraded two other RHEL4 servers to 4.5.7 and those zmdbintegrityreports were clean.

Before I freaked out, I wanted to verify the tables were still there so I ran mysql cli:

# use mboxgroup10; (and several other listed below)
# show tables;
mysql> show tables;
+-----------------------+
| Tables_in_mboxgroup10 |
+-----------------------+
| appointment           | 
| mail_item             | 
| open_conversation     | 
| pop3_message          | 
| tombstone             | 
+-----------------------+
5 rows in set (0.00 sec)

Breathing better now :-)

So, the tables are all there and when I login to zimbra, I haven't lost any calendars, so it would appear that the zmdbintegrityreport is getting confused.

I manually ran /opt/zimbra/libexec/zmdbintegrityreport and got the same errors.

Any idea where to look to debug zmdbintegrityreport?

Thanks,
John

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=[snip]
mailbox10.appointment
 error    : Table 'mailbox10.appointment' doesn't exist
 mailbox10.mail_item
 error    : Table 'mailbox10.mail_item' doesn't exist
 mailbox10.open_conversation
 error    : Table 'mailbox10.open_conversation' doesn't exist
 mailbox10.tombstone
 error    : Table 'mailbox10.tombstone' doesn't exist
 mailbox11.appointment
 error    : Table 'mailbox11.appointment' doesn't exist
 mailbox11.mail_item
 error    : Table 'mailbox11.mail_item' doesn't exist
 mailbox11.open_conversation
 error    : Table 'mailbox11.open_conversation' doesn't exist
 mailbox11.tombstone
 error    : Table 'mailbox11.tombstone' doesn't exist
 mailbox12.appointment
 error    : Table 'mailbox12.appointment' doesn't exist
 mailbox12.mail_item
 error    : Table 'mailbox12.mail_item' doesn't exist
 mailbox12.open_conversation
 error    : Table 'mailbox12.open_conversation' doesn't exist
 mailbox12.tombstone
 error    : Table 'mailbox12.tombstone' doesn't exist
  mailbox9.appointment
 error    : Table 'mailbox9.appointment' doesn't exist
 mailbox9.mail_item
 error    : Table 'mailbox9.mail_item' doesn't exist

[snip...]

 mailbox9.open_conversation
 error    : Table 'mailbox9.open_conversation' doesn't exist
 mailbox9.tombstone
 error    : Table 'mailbox9.tombstone' doesn't exist
 mailbox90.appointment
 error    : Table 'mailbox90.appointment' doesn't exist
 mailbox90.mail_item
 error    : Table 'mailbox90.mail_item' doesn't exist
 mailbox90.open_conversation
 error    : Table 'mailbox90.open_conversation' doesn't exist
 mailbox90.tombstone
 error    : Table 'mailbox90.tombstone' doesn't exist
 mailbox91.appointment
 error    : Table 'mailbox91.appointment' doesn't exist
 mailbox91.mail_item
 error    : Table 'mailbox91.mail_item' doesn't exist
 mailbox91.open_conversation
 error    : Table 'mailbox91.open_conversation' doesn't exist
 mailbox91.tombstone
 error    : Table 'mailbox91.tombstone' doesn't exist

[jdell]

I just realized I totally overlooked the naming used for the db's. I had just used the mysql 'show databases;' to see list of db's.

Could that be the issue?