Planet MySQL Planet MySQL: Meta Deutsch Español Français Italiano 日本語 Русский Português 中文
Showing entries 1 to 3

Displaying posts with tag: mysql_upgrade (reset)

On Upgrades to Percona Server 5.7 GA: CentOS 6 Case
+1 Vote Up -0Vote Down

As you probably noted, Percona had finally released Percona Server 5.7 GA two days ago. I had not paid much attention to this branch during last month or so, but as it's GA now I decided to check what's there, how it works and install/upgrade different boxes and VMs to use it.

For testing purposes and for this series of blog posts I am going to build it from Git source (at least on Fedora Core 23), upgrade to it on 32-bit …

  [Read more...]
MariaDB 10.0 upgrade goes smoothly
+0 Vote Up -0Vote Down

I have been meaning to update some systems to MariaDB 10.0 and finally had a bit of time to get around to that.  The documentation of specifics of what’s needed to go from MariaDB 5.5 to 10.0 can be found here and while it’s not very long it seems there’s little to actually do. Having already … Continue reading MariaDB 10.0 upgrade goes smoothly

MySQL Workbench Stuck in Fetching Mode
+3 Vote Up -0Vote Down

Another obscure issue I ran into not long ago was when using MySQL Workbench, and clicking on a table, it became stuck in fetching mode.

What triggered the issue was a recent MySQL upgrade, but MySQL itself, not Workbench.

After checking the error log, we saw an error like:

Incorrect definition of table mysql.proc: expected column
'comment' at position 15 to have type text, found type char(64)

Instantly, I knew mysql_upgrade needed to be ran in order to fix the “Incorrect definition” issue, and turns out that is the root cause for Workbench getting stuck in the “fetching” mode.

So the solution is to run mysql_upgrade. Should that not fix …

  [Read more...]
Showing entries 1 to 3

Planet MySQL © 1995, 2016, Oracle Corporation and/or its affiliates   Legal Policies | Your Privacy Rights | Terms of Use

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.