Bug 17579 - mga6: Error: Column last_update in table "mysql"."innodb_table_stats" should be BINARY(4)
Summary: mga6: Error: Column last_update in table "mysql"."innodb_table_stats" should...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: AL13N
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-22 10:12 CET by Bit Twister
Modified: 2016-02-12 00:37 CET (History)
0 users

See Also:
Source RPM: mariadb-10.1.10-1.mga6.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2016-01-22 10:12:00 CET 
Description of problem:

 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).

 InnoDB: Error: Fetch of persistent statistics requested for table "mysql"."gtid_slave_pos" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.

Version-Release number of selected component (if applicable):


How reproducible: always


Steps to Reproduce:
1. grep Error /var/log/mysqld/*


Reproducible: 

Steps to Reproduce:
Comment 1 Bit Twister 2016-02-02 19:10:33 CET 
The bug is only on a mga5->mga6 upgrade. Problem is not on a clean mga6 install.
Samuel Verschelde 2016-02-03 10:22:49 CET

Assignee: bugsquad => alien
Severity: normal => major

Comment 2 David Walser 2016-02-11 22:52:17 CET 
Did you run mysql_upgrade?
Comment 3 Bit Twister 2016-02-12 00:37:08 CET 
(In reply to David Walser from comment #2)
> Did you run mysql_upgrade?

No, this is my very first upgrade test just to help reduce QA's load.
I usually only do clean installs. 

   mysql_upgrade --user=secret_squirrel --password='top_secret'
   systemctl stop mysqld
   systemctl start mysqld
   grep -i error /var/log/mysqld/*

Probably would not hurt to drop a line or two in the release or errata document.

Sorry for wasting your time.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.