Upgrade v9.6 to v10.5 and mysqlDB migration failure

I am coming from MM version 9.6 upgrading to 10.5. Last upgrades were a breeze, which I love, but my neglect to upgrade lately and having to jump to 10.5, just doing the simply upgrades failed because there are DB changes. Jumping the gun!

Anyway, after reading the [important-upgrade-notes]. (Important Upgrade Notes - Mattermost documentation)
I can see there are changes in the DB, and I would like to know if I did this correctly. IT did work, but needed a little extra mysql_upgrade -root -p at the end because there was a complaint in the logs when I tried to systemctl start mattermost

Cannot load from mysql.proc. The table is probably corrupted

I took the db commands from v10.6 in the ā€˜important-upgrade-notesā€™, vim them in a file.sql and did mysql -uroopt -p mattermost < file.sql, which did target the mattermost db and created the new tables with ect.

But once I continued with the upgrade steps, it still crashed with the error above. Only searching online about ā€˜Cannot load from mysql.proc. The table is probably corruptedā€™ led me to run mysql_upgrade -root -p. All is good.

I canā€™t be the only one running into this? And what exactly happens here, mysql refreshes its cache of tables so starting mattermost will read them properly? I am curiousā€¦

Sucks that V11 you need to use psql cause I was just fine with mysql, even though Iā€™m sure psql will probably introduce performance improvements.

2 Likes

Our recommended upgrade strategy is to get to the first available ESR (9.11.9) and then go to 10.5.1

2 Likes