Re: problems upgrading 5.7 -> 8.0.15
Hello,
had a new testcandidate today which is not working. In last weeks a i did a few upgrades which worked, apart from a really slow and lengthy process...
today i see this in logs:
2019-04-23T13:31:59.797653+02:00 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.15) starting as process 23689
2019-04-23T13:43:17.806794+02:00 2 [ERROR] [MY-012069] [InnoDB] table: mytable has 25 columns but InnoDB dictionary has 26 columns
2019-04-23T13:43:17.807443+02:00 2 [ERROR] [MY-010767] [Server] Error in fixing SE data for mydb.mytable
2019-04-23T13:54:19.213705+02:00 0 [ERROR] [MY-010022] [Server] Failed to Populate DD tables.
2019-04-23T13:54:19.213963+02:00 0 [ERROR] [MY-010119] [Server] Aborting
mysqlupgradechecker did not check this.
It took ~10 minutes to get to this point and packacke installation failed, no chance to start up.
After that i restored all binary data by snapshot. So iam at the point with a working mysql 5.7 installation again. To compare i installed mariadb 10.3 with their repo and this worked really fast and without problems. to remember, even a working upgrade to mysql 8.0 needs long minutes...
Next step was again to go back to working mysql 5.7 installation.
i dumped all data to sql, removed all data from mysql and installed data again by importing the sql. After this was finished i tried again upgrade to mysql 8.0 and now it worked. I think by importing sql all corrupt data was removed and we have a working and upgradeable database. corrupt data may result from former bugs, but was working in this condition in mysql 5.7.
But i cant do this effort every time. exporting/importing of huge data may need hours. It should work also by updating binary data, either by telling about errors by using upgradechecker or by just working.
For me upgradeprocess from 5.7 to 8.0 is still broken and we think about switching to mariadb. I dont like this, but we need a reliable base.
I can do further tests if you suggest.
Thanks,
Hans