Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not a Bug
    • 10.9.4
    • N/A
    • Upgrades
    • None

    Description

      mysql_upgrade
      Phase 1/7: 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
      Error : Table 'mysql.gtid_slave_pos' doesn't exist in engine
      status : Operation failed
      mysql.help_category OK
      mysql.help_keyword OK
      mysql.help_relation OK
      mysql.help_topic OK
      mysql.index_stats OK
      mysql.innodb_index_stats
      Error : Table 'mysql.innodb_index_stats' doesn't exist in engine
      status : Operation failed
      mysql.innodb_table_stats
      Error : Table 'mysql.innodb_table_stats' doesn't exist in engine
      status : Operation failed
      mysql.plugin OK
      mysql.proc OK
      mysql.procs_priv OK
      mysql.proxies_priv OK
      mysql.roles_mapping OK
      mysql.servers 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

      Repairing tables
      mysql.gtid_slave_pos
      Error : Table 'mysql.gtid_slave_pos' doesn't exist in engine
      status : Operation failed
      mysql.innodb_index_stats
      Error : Table 'mysql.innodb_index_stats' doesn't exist in engine
      status : Operation failed
      mysql.innodb_table_stats
      Error : Table 'mysql.innodb_table_stats' doesn't exist in engine
      status : Operation failed
      Phase 2/7: Installing used storage engines... Skipped
      Phase 3/7: Fixing views
      mysql.user
      Error : The user specified as a definer ('mariadb.sys'@'localhost') does not exist
      error : Corrupt
      sys.host_summary OK
      sys.host_summary_by_file_io OK
      sys.host_summary_by_file_io_type OK
      sys.host_summary_by_stages OK
      sys.host_summary_by_statement_latency OK
      sys.host_summary_by_statement_type OK
      sys.innodb_buffer_stats_by_schema OK
      sys.innodb_buffer_stats_by_table OK
      sys.innodb_lock_waits OK
      sys.io_by_thread_by_latency OK
      sys.io_global_by_file_by_bytes OK
      sys.io_global_by_file_by_latency OK
      sys.io_global_by_wait_by_bytes OK
      sys.io_global_by_wait_by_latency OK
      sys.latest_file_io OK
      sys.memory_by_host_by_current_bytes OK
      sys.memory_by_thread_by_current_bytes OK
      sys.memory_by_user_by_current_bytes OK
      sys.memory_global_by_current_bytes OK
      sys.memory_global_total OK
      sys.metrics OK
      sys.processlist OK
      sys.ps_check_lost_instrumentation OK
      sys.schema_auto_increment_columns OK
      sys.schema_index_statistics OK
      sys.schema_object_overview OK
      sys.schema_redundant_indexes OK
      sys.schema_table_lock_waits OK
      sys.schema_table_statistics OK
      sys.schema_table_statistics_with_buffer OK
      sys.schema_tables_with_full_table_scans OK
      sys.schema_unused_indexes OK
      sys.session OK
      sys.session_ssl_status OK
      sys.statement_analysis OK
      sys.statements_with_errors_or_warnings OK
      sys.statements_with_full_table_scans OK
      sys.statements_with_runtimes_in_95th_percentile OK
      sys.statements_with_sorting OK
      sys.statements_with_temp_tables OK
      sys.user_summary OK
      sys.user_summary_by_file_io OK
      sys.user_summary_by_file_io_type OK
      sys.user_summary_by_stages OK
      sys.user_summary_by_statement_latency OK
      sys.user_summary_by_statement_type OK
      sys.version OK
      sys.wait_classes_global_by_avg_latency OK
      sys.wait_classes_global_by_latency OK
      sys.waits_by_host_by_latency OK
      sys.waits_by_user_by_latency OK
      sys.waits_global_by_latency OK
      sys.x$host_summary OK
      sys.x$host_summary_by_file_io OK
      sys.x$host_summary_by_file_io_type OK
      sys.x$host_summary_by_stages OK
      sys.x$host_summary_by_statement_latency OK
      sys.x$host_summary_by_statement_type OK
      sys.x$innodb_buffer_stats_by_schema OK
      sys.x$innodb_buffer_stats_by_table OK
      sys.x$innodb_lock_waits OK
      sys.x$io_by_thread_by_latency OK
      sys.x$io_global_by_file_by_bytes OK
      sys.x$io_global_by_file_by_latency OK
      sys.x$io_global_by_wait_by_bytes OK
      sys.x$io_global_by_wait_by_latency OK
      sys.x$latest_file_io OK
      sys.x$memory_by_host_by_current_bytes OK
      sys.x$memory_by_thread_by_current_bytes OK
      sys.x$memory_by_user_by_current_bytes OK
      sys.x$memory_global_by_current_bytes OK
      sys.x$memory_global_total OK
      sys.x$processlist OK
      sys.x$ps_digest_95th_percentile_by_avg_us OK
      sys.x$ps_digest_avg_latency_distribution OK
      sys.x$ps_schema_table_statistics_io OK
      sys.x$schema_flattened_keys OK
      sys.x$schema_index_statistics OK
      sys.x$schema_table_lock_waits OK
      sys.x$schema_table_statistics OK
      sys.x$schema_table_statistics_with_buffer OK
      sys.x$schema_tables_with_full_table_scans OK
      sys.x$session OK
      sys.x$statement_analysis OK
      sys.x$statements_with_errors_or_warnings OK
      sys.x$statements_with_full_table_scans OK
      sys.x$statements_with_runtimes_in_95th_percentile OK
      sys.x$statements_with_sorting OK
      sys.x$statements_with_temp_tables OK
      sys.x$user_summary OK
      sys.x$user_summary_by_file_io OK
      sys.x$user_summary_by_file_io_type OK
      sys.x$user_summary_by_stages OK
      sys.x$user_summary_by_statement_latency OK
      sys.x$user_summary_by_statement_type OK
      sys.x$wait_classes_global_by_avg_latency OK
      sys.x$wait_classes_global_by_latency OK
      sys.x$waits_by_host_by_latency OK
      sys.x$waits_by_user_by_latency OK
      sys.x$waits_global_by_latency OK
      Phase 4/7: Running 'mysql_fix_privilege_tables'
      ERROR 1932 (42S02) at line 482: Table 'mysql.innodb_index_stats' doesn't exist in engine
      FATAL ERROR: Upgrade failed

      Attachments

        Activity

          danblack Daniel Black added a comment -

          mokraemer what was the previous version running? Was mariadb-upgrade/mysql_upgrade run on that version? What version of MariaDB/MySQL was the original datadir installation from?

          danblack Daniel Black added a comment - mokraemer what was the previous version running? Was mariadb-upgrade/mysql_upgrade run on that version? What version of MariaDB/MySQL was the original datadir installation from?

          It is a long shot, but if the old version was MariaDB 10.4 or MySQL 5.7 or earlier, then this report might be a duplicate of MDEV-24412.

          marko Marko Mäkelä added a comment - It is a long shot, but if the old version was MariaDB 10.4 or MySQL 5.7 or earlier, then this report might be a duplicate of MDEV-24412 .
          mokraemer Marc added a comment -

          Yes, it was 10.5.18; so it is a duplicate - thanks. So i'm waiting for 10.9.5 to get this fixed?

          mokraemer Marc added a comment - Yes, it was 10.5.18; so it is a duplicate - thanks. So i'm waiting for 10.9.5 to get this fixed?
          marko Marko Mäkelä added a comment - - edited

          MDEV-24412 affects the upgrade from 10.4 or an earlier version to 10.5 or a later version, when using innodb_log_files_in_group>1. Because you upgraded from 10.5.18, the reason for the failed upgrade must be something else. Can you please try to check the error log of the MariaDB server? If your operating system uses systemd, the command journalctl -xe should show something.

          My next guess would be that the 10.5.18 server had not been shut down, or you are trying to start up 10.9.4 on a backup of the 10.5.18 server, on which mariadb-backup --prepare had not been run using the 10.5 (or 10.6 or 10.7) version of the backup tool.

          marko Marko Mäkelä added a comment - - edited MDEV-24412 affects the upgrade from 10.4 or an earlier version to 10.5 or a later version, when using innodb_log_files_in_group>1 . Because you upgraded from 10.5.18, the reason for the failed upgrade must be something else. Can you please try to check the error log of the MariaDB server? If your operating system uses systemd, the command journalctl -xe should show something. My next guess would be that the 10.5.18 server had not been shut down, or you are trying to start up 10.9.4 on a backup of the 10.5.18 server, on which mariadb-backup --prepare had not been run using the 10.5 (or 10.6 or 10.7) version of the backup tool.
          mokraemer Marc added a comment -

          I think sth. with innodb_index_stats and innodb_table_stats was corrupted. Just dropped both tables and rerun mysql_upgrade which now worked as expected.

          Sorry, I think you can close this - thanks for your help.

          mokraemer Marc added a comment - I think sth. with innodb_index_stats and innodb_table_stats was corrupted. Just dropped both tables and rerun mysql_upgrade which now worked as expected. Sorry, I think you can close this - thanks for your help.

          People

            Unassigned Unassigned
            mokraemer Marc
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.