Errors mysql After Upgrade to 8.7
Re: Errors mysql After Upgrade to 8.7
Thanks mefistoteles, your steps worked as a charm
Re: Errors mysql After Upgrade to 8.7
Thanks for posting a solution - it appears to have help resolve the issue.
I ran into these db errors after upgrading from 8.5.1 to 8.7.11.
Note, I restarted all the services after following the steps.
I ran into these db errors after upgrading from 8.5.1 to 8.7.11.
Note, I restarted all the services after following the steps.
- tonster
- Zimbra Employee
- Posts: 313
- Joined: Fri Feb 21, 2014 10:14 am
- Location: Ypsilanti, MI
- ZCS/ZD Version: Release 8.7.0_GA_1659.RHEL6_64_2016
Re: Errors mysql After Upgrade to 8.7
Hopefully you've also fixed your corrupt databases and aren't just running normally with innodb_force_recovery=5 all the time.Himanshu_N wrote:Ok. I this thing Done after bit of struggle.
It had Two issues.
1.Had to Increase innodb_force_recovery (in my.cnf) upto 5 in a step by step manner.
2.mysql -u root --password=$mysql_root_password
3.USE mboxgroup9; ( Database which reported Tabel as Corrupt)
4.OPTIMIZE TABLE open_conversation;
5.Repeated for all such tables which were reported as corrupt in
/opt/zimbra/libexec/zmdbintegrityreport -r
And Finally Applied Upgrade
6./opt/zimbra/common/bin/mysql_upgrade -u root -p
7.And Upgrade to 8.7.xx was Successful.
Above Issue of open_Conversation was resulting in Mobile Client Unable to Sync using Imap & Slowed Performance .