Best course of action for missing/corrupted tables?

[jimbo]

Running Zimbra OSE 5.11 on RedHat EL 5.3

The system is sending and receiving mail fine, however changes to preferences etc do not persist after nightly shutdown for backup.

Need some advice on the best way of repairing some mysql tables. After a hard server crash some odd behavior I checked for corrupted disk and a few other things. Ran a check on the database after receiving an error during an attempt to upgrade to 6.x. Restored from backup and ran the following:

/opt/zimbra/mysql/bin/mysqlcheck --defaults-file=/opt/zimbra/conf -S /opt/zimbra/db/mysql.sock -A -C -s -u root --password --all-databases --auto-repair

which output the following:

mboxgroup25.appointment
Error    : Table 'mboxgroup25.appointment' doesn't exist
error    : Corrupt
mboxgroup25.data_source_item
Error    : Table 'mboxgroup25.data_source_item' doesn't exist
error    : Corrupt
mboxgroup25.imap_folder
Error    : Table 'mboxgroup25.imap_folder' doesn't exist
error    : Corrupt
mboxgroup25.imap_message
Error    : Table 'mboxgroup25.imap_message' doesn't exist
error    : Corrupt
mboxgroup25.mail_item
Error    : Table 'mboxgroup25.mail_item' doesn't exist
error    : Corrupt
mboxgroup25.open_conversation
Error    : Table 'mboxgroup25.open_conversation' doesn't exist
error    : Corrupt
mboxgroup25.pop3_message
Error    : Table 'mboxgroup25.pop3_message' doesn't exist
error    : Corrupt
mboxgroup25.revision
Error    : Table 'mboxgroup25.revision' doesn't exist
error    : Corrupt
mboxgroup25.tombstone
Error    : Table 'mboxgroup25.tombstone' doesn't exist
error    : Corrupt
zimbra.mobile_devices
Error    : Table 'zimbra.mobile_devices' doesn't exist
error    : Corrupt
mboxgroup25.appointment
Error    : Table 'mboxgroup25.appointment' doesn't exist
error    : Corrupt
mboxgroup25.data_source_item
Error    : Table 'mboxgroup25.data_source_item' doesn't exist
error    : Corrupt
mboxgroup25.imap_folder
Error    : Table 'mboxgroup25.imap_folder' doesn't exist
error    : Corrupt
mboxgroup25.imap_message
Error    : Table 'mboxgroup25.imap_message' doesn't exist
error    : Corrupt
mboxgroup25.mail_item
Error    : Table 'mboxgroup25.mail_item' doesn't exist
error    : Corrupt
mboxgroup25.open_conversation
Error    : Table 'mboxgroup25.open_conversation' doesn't exist
error    : Corrupt
mboxgroup25.pop3_message
Error    : Table 'mboxgroup25.pop3_message' doesn't exist
error    : Corrupt
mboxgroup25.revision
Error    : Table 'mboxgroup25.revision' doesn't exist
error    : Corrupt
mboxgroup25.tombstone
Error    : Table 'mboxgroup25.tombstone' doesn't exist
error    : Corrupt
zimbra.mobile_devices
Error    : Table 'zimbra.mobile_devices' doesn't exist
error    : Corrupt

What's the best method of fixing this?

Thanks!

jimbo

[dcampbell]

Ever figure this out?

[RaNd]

Same errors here, while upgrading from 4.5.11 to 5.0.21 on Ubuntu 6.06

[uxbod]

Have you tried performing a mysql table repair ?

[RaNd]

In my case all tables are ok.
And when i tried to repair "Table 'mboxgroup25.pop3_message" returned table not found...

[RaNd]

Also tried 5.0.20 and problem persists...

Any ideas about how to remove/repair these tables ??

[jimbo]

In my case I had gotten the mboxgroupXX.pop3_message table not found as well.
I think what had happened in my case was that an upgrade had failed and instead of blowing away the entire /opt/zimbra directory structure I just restored from backup over the existing data. This left some mysql file directories that did not appear in the original schema and hence the errors.

Procede at your own risk!!! Make sure you have a good backup!!!

I cannot stress that enough!!

So the fix for me was (having a GOOD BACKUP) deleting the table diretories that are missing in /opt/zimbra/db/data/ such as mboxgroup25/pop3_message.*

Then run the repair on the database and when you have no errors you should be able to upgrade successfully.

Hope this helps.

jimbo