Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.3(EOL), 10.4(EOL)
-
None
-
Rhel7
Description
I got the following errors when trying to upgrade from old version to 10.3. It happens during phase 3 but it is not FATAL and the upgrade finished successfully:
Phase 1/7: Checking and upgrading mysql database
....
Phase 2/7: Installing used storage engines... Skipped
Phase 3/7: Fixing views
......
db.domainpaths
Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 100215, now running 100313. Please use mysql_upgrade to fix this error
error : Corrupt
db.domainpreviewview
Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 100215, now running 100313. Please use mysql_upgrade to fix this error
error : Corrupt
db.domainprofileview OK
.....
Phase 7/7: Running 'FLUSH PRIVILEGES'
OK
12/12/2019 15:05:57 : MariaDB server is upgraded successfully!
Step to duplicate:
- Install old version 10.1/10.2
- Stop MariaDB
- Remove old installation:
rpm -e --nodeps $(rpm -qa 'mysql*') 2>/dev/null
rpm -e --nodeps $(rpm -qa 'mariadb*') 2>/dev/null
rpm -e --nodeps $(rpm -qa 'MariaDB*') 2>/dev/null
rpm -e --nodeps $(rpm -qa 'jemalloc*') 2>/dev/null
rpm -e --nodeps $(rpm -qa 'galera*') 2>/dev/null - remove old configuration: rm -rf /etc/init.d/mysql.rpmsave
- Install new version 10.3
- Start MariaDB
- Run mysql_upgrade
Running mysql_upgrade again as suggestion shows:
This installation of MySQL is already upgraded to 10.3.21-MariaDB, use --force if you still need to run mysql_upgrade
If I force the 2nd upgrade, sometimes everything is run ok, but sometimes the upgrade hang and it never finishes.
Attachments
Issue Links
- relates to
-
-
- Closed
-
Activity
Thanks for the report. I think the error should be innocent. Apparently the reason is that your views call stored functions, and mysql_upgrade runs REPAIR on user views before it upgrades system tables.
I'll assign it to sanja to see if there is anything that can be done about the error, it's not pretty and a valid cause of concern for a user.
My main concern is whether this is just Error message or is there any potential problem ? Because even with the error showing up, the Database seems to function normally without issue so far.