Bug #77756 Mysql Workbench: Can not obtain tables list
Submitted: 17 Jul 2015 1:14 Modified: 26 Jan 2016 8:41
Reporter: A A Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S1 (Critical)
Version:6.3.4 OS:Windows (Microsoft Windows 7 Ultimate Service Pack 1)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[17 Jul 2015 1:14] A A
Description:
Can not use Workbench with our server:

Error loading schema content	Error Code: 1558 Column count of mysql.proc is wrong. Expected 20, found 16. Created with MySQL 50167, now running 50529. Please use mysql_upgrade to fix this error.	

PhpMyAdmin workfine. This is the production server that I can not edit. Database I connected to works great for many years.

Please just do as many as you can. Do not force users to do something with server before using your software.

How to repeat:
*
[17 Jul 2015 1:31] MySQL Verification Team
Thank you for the bug report. Against which server version WorkBench connected to?. It's that server upgraded?. Thanks.
[17 Jul 2015 1:50] A A
The server version is 5.5.29-29.4-log. I don't know wasit updated or not. I just know it work fine.
[17 Jul 2015 1:53] MySQL Verification Team
Thank you for the feedback. If you are not the Server administrator please contact him/she, ask it was done an upgrade and if yes to run mysql_upgrade. Thanks.
[17 Jul 2015 2:09] A A
I am not an administrator. Administrator said he will not run anything on production database. 

I tried two other GUI tools and they work fine.
[17 Jul 2015 10:45] MySQL Verification Team
Thank you for the report.
Could you please provide full wb.log to investigate this further? Moreover from error messages this looks as if Server was upgraded from 5.1.67 to 5.5.29 but mysql_upgrade was never invoked which could have fixed this issue. Some client applications don't detect this but WB detected it.

Thanks,
Umesh
[21 Jul 2015 1:17] A A
Last lines in the wb.log are:

11:11:22 [INF][      Workbench]: UI is up
11:11:22 [INF][      Workbench]: Running the application
11:11:29 [INF][      SqlEditor]: Opened connection 'amayama.com' to Percona Server (GPL), Release rel29.4, Revision 401 version 5.5.29-29.4-log
11:11:31 [INF][     AutoCCache]: Initializing autocompletion cache for amayama.com
11:11:31 [INF][        WQE.net]: Launching SQL IDE
11:11:32 [INF][        WQE.net]: SQL IDE UI is ready
11:11:33 [ERR][SqlEditorSchemaTree]: Exception querying metadata from mysql.proc, will fallback to SHOW PROCEDURE: Exception: SELECT command denied to user 'xxx'@'xx.xx.xx.xx' for table 'proc'
11:11:33 [ERR][SqlEditorSchemaTree]: SQLException executing Error loading schema content: Error Code: 1558
Column count of mysql.proc is wrong. Expected 20, found 16. Created with MySQL 50167, now running 50529. Please use mysql_upgrade to fix this error.

Hope this information will be useful. We can not manage neither MySQL server, nor user permissions.

Thanks.
[22 Jul 2015 6:32] MySQL Verification Team
Thank you for the feedback.
Observed similar error when upgraded from 5.1.76->5.5.46, without mysql_upgrade used:

11:54:24 [INF][      Workbench]: UI is up
11:54:25 [INF][      Workbench]: Running the application
11:54:36 [INF][      SqlEditor]: Opened connection 'x.x.x.x' to MySQL Community Server (GPL) version 5.5.46
11:54:38 [INF][     AutoCCache]: Initializing autocompletion cache for x.x.x.x
11:54:39 [INF][        WQE.net]: Launching SQL IDE
11:54:40 [INF][        WQE.net]: SQL IDE UI is ready
11:54:41 [ERR][SqlEditorSchemaTree]: Exception querying metadata from mysql.proc, will fallback to SHOW PROCEDURE: Exception: SELECT command denied to user 'ushastry'@'x.x.x.x' for table 'proc'
11:54:42 [ERR][SqlEditorSchemaTree]: SQLException executing Error loading schema content: Error Code: 1548
Cannot load from mysql.proc. The table is probably corrupted
11:57:08 [ERR][SqlEditorSchemaTree]: SQLException executing Error loading schema content: Error Code: 1548
Cannot load from mysql.proc. The table is probably corrupted
[26 Jan 2016 8:41] Marcin Szalowicz
Hi A A, 
Your database is in unstable state, and needs maintenance which is running mysql_upgrade. After fixing this, Workbench should work properly.  
Keep in mind that not fixing this may cause other unexpected problems in the server.