[MDEV-31288] MariaDB-upgrade command fails Created: 2023-05-16  Updated: 2023-08-31  Resolved: 2023-05-16

Status: Closed
Project: MariaDB Server
Component/s: Upgrades
Affects Version/s: 10.6.12
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Pon Suresh Pandian (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Rocky Linux 8


Attachments: Text File mariadb-upgrade-output.log     File mariadb_custom_server.cnf    
Issue Links:
Duplicate
duplicates MDEV-28915 mysql_upgrade fails due to old_mode="... Closed

 Description   

Hi Team,

Currently I have one primary / replica server, installed with MariaDB 10.4.16 CS version..

Now I want to add two read replicas 10.6 ES version under 10.4 CS master server.. So I took mysqldump(backup) from 10.4 server and restored to 10.6 ES server..

Backup Command :

mysqldump -u root -p'xxx' --routines --events --triggers --master-data=2 --single-transaction --all-databases > fullbackup.sql

Restore Command :

mysql -u root -p'xxx' < fullbackup.sql

Then I ran mariadb-upgrade command.. It throws errors, here I attached complete upgrade logs..

Then I tried with commenting below three lines and I had the same errors,

#character-set-server=utf8mb4
#collation-server=utf8mb4_general_ci
#init-connect='SET NAMES utf8mb4'

I then tried "old_mode" to empty

old_mode=""

And mariadb-upgrade ran OK. Later I tried to uncomment the first 3 lines (character-set) and just keep old_mode="" it ran OK too..

character-set-server=utf8mb4
collation-server=utf8mb4_general_ci
init-connect='SET NAMES utf8mb4'
old_mode=""


Generated at Thu Feb 08 10:22:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.