[MDEV-21332] Error message when upgrading from 10.1 or 10.2 to 10.3 Created: 2019-12-17  Updated: 2023-04-27

Status: Confirmed
Project: MariaDB Server
Component/s: Scripts & Clients
Affects Version/s: 10.3, 10.4
Fix Version/s: 10.4

Type: Bug Priority: Minor
Reporter: Nguyen Dang Thien Assignee: Oleksandr Byelkin
Resolution: Unresolved Votes: 0
Labels: None
Environment:

Rhel7

Issue Links:
Relates
relates to MDEV-14573 Upgrade from previous versions is bro... Closed

 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:

mysql_upgrade log

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.

 Comments   
Comment by Nguyen Dang Thien [ 2019-12-17 ]

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.

Comment by Elena Stepanova [ 2019-12-18 ]

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.

Generated at Thu Feb 08 09:06:20 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.