"Duplicate entry" error when upgrading MariaDB 10.6 to 11.4
2
votes
1
answer
44
views
I was trying to upgrade my local development environment (Ubuntu 22.04 WSL) from MariaDB 10.6 to 11.4.
After updating the APT repo file, I run and
apt update
, which updated the server version.
However, upon running mariadb-upgrade
, I see this error:
Phase 1/8: Checking and upgrading mysql database
Processing databases
mysql
mysql.column_stats OK
mysql.columns_priv OK
mysql.db OK
mysql.event OK
mysql.func OK
mysql.global_priv OK
mysql.gtid_slave_pos OK
mysql.help_category OK
mysql.help_keyword OK
mysql.help_relation OK
mysql.help_topic OK
mysql.index_stats OK
mysql.innodb_index_stats OK
mysql.innodb_table_stats OK
mysql.plugin OK
mysql.proc OK
mysql.procs_priv OK
mysql.proxies_priv OK
mysql.roles_mapping OK
mysql.servers OK
mysql.spider_link_failed_log OK
mysql.spider_link_mon_servers OK
mysql.spider_table_crd OK
mysql.spider_table_position_for_recovery OK
mysql.spider_table_sts OK
mysql.spider_tables OK
mysql.spider_xa OK
mysql.spider_xa_failed_log OK
mysql.spider_xa_member OK
mysql.table_stats OK
mysql.tables_priv OK
mysql.time_zone OK
mysql.time_zone_leap_second OK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_type OK
mysql.transaction_registry OK
Phase 2/8: Installing used storage engines... Skipped
Phase 3/8: Running 'mysql_fix_privilege_tables'
ERROR 1062 (23000) at line 30: Duplicate entry 'db_626suite-get_98_53_metadata-PROCEDURE' for key 'PRIMARY'
ERROR 1062 (23000) at line 256: Duplicate entry 'db_626suite-get_98_53_metadata-PROCEDURE' for key 'PRIMARY'
ERROR 1062 (23000) at line 304: Duplicate entry 'db_626suite-get_98_53_metadata-PROCEDURE' for key 'PRIMARY'
ERROR 1062 (23000) at line 331: Duplicate entry 'db_626suite-get_98_53_metadata-PROCEDURE' for key 'PRIMARY'
ERROR 1062 (23000) at line 343: Duplicate entry 'db_626suite-get_98_53_metadata-PROCEDURE' for key 'PRIMARY'
FATAL ERROR: Upgrade failed
I do not understand how it is possible that there are duplicate functions, nor how to solve the problem.
Since this is just a development environment, I simply tried dropping the database, but the error persists.
Maybe the new version performs some checks that the old one didn't; but, how can I check for similar inconsistencies before running mariadb-upgrade
in order to get a smooth update?
Asked by Matteo Tassinari
(187 rep)
May 6, 2025, 02:13 PM
Last activity: May 6, 2025, 02:55 PM
Last activity: May 6, 2025, 02:55 PM