[SOLVED] zmdbintegrityreport reports missing tables

[landrypm]

zmdbintegrityreport is giving the attached output. Basically it is complaining that some tables in the mboxgroup2, 3, and 4 databases do not exist. There are directories in /opt/zimbra/db/data named mboxgroup[2,3,4] but the files within have not changed in a very long time (since original installation?).

I am about to upgrade from 5.1.6 to 5.0.22. Is there anything I can do to correct this error as part of my upgrade process?

--
patrick

ZCS 5.0.16, RHEL5

[uxbod]

Okay; something is not quite right there. Please try the following

su - zimbra
mysql
use zimbra;
select group_id, comment from mailbox where group_id = '2';

The comment field should show which account is having issues; therefore the account it returns is that still a valid account ? Please do the same for 3 and 4.

[uxbod]

Oops I missed the most important bit!

error    : Corrupt

Sounds like your database requires a bit of TLC. To start with try the following

su - zimbra
mysql
use mboxgroup2;
repair table appointment;
check table appointment;

If that comes back as Okay then let us know and we can then repair all your tables

[landrypm]

Thanks for the quick reply. I am in the middle of full backups right now. I will check it out as soon as I can bring the server back up.

[landrypm]

I can list the tables and it shows appointment being there but repair and check both fail.


mysql> use mboxgroup2;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> repair table appointment;
+------------------------+--------+----------+----------------------------------------------+
| Table | Op | Msg_type | Msg_text |
+------------------------+--------+----------+----------------------------------------------+
| mboxgroup2.appointment | repair | Error | Table 'mboxgroup2.appointment' doesn't exist |
| mboxgroup2.appointment | repair | error | Corrupt |
+------------------------+--------+----------+----------------------------------------------+
2 rows in set (0.00 sec)

mysql> check table appointment;
+------------------------+-------+----------+----------------------------------------------+
| Table | Op | Msg_type | Msg_text |
+------------------------+-------+----------+----------------------------------------------+
| mboxgroup2.appointment | check | Error | Table 'mboxgroup2.appointment' doesn't exist |
| mboxgroup2.appointment | check | error | Corrupt |
+------------------------+-------+----------+----------------------------------------------+
2 rows in set (0.00 sec)

mysql> show tables in mboxgroup2;
+----------------------+
| Tables_in_mboxgroup2 |
+----------------------+
| appointment |
| data_source_item |
| imap_folder |
| imap_message |
| mail_item |
| open_conversation |
| pop3_message |
| revision |
| tombstone |
+----------------------+
9 rows in set (0.00 sec)

mysql>

[tansyuan]

Same same, encountering same issue. Any advise yet?

[landrypm]

This issue was resolved with help from Zimbra tech support. Unfortunately since my mail server was down I used gmail for our support conversation and gmail has already expired the conversation. I do remember that the solution was to stop the mysql server and then physically remove the database files for the corrupt tables. Apparently Zimbra will re-create them as necessary.