MySQL Bugs: #64546: Object Browser in Workbench not displaying schemas

Bug #64546	Object Browser in Workbench not displaying schemas
Submitted:	5 Mar 2012 12:24	Modified:	4 May 2012 1:19
Reporter:	Martin O'Shea	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	5.2.38 Rev 8753	OS:	Windows (Windows 7 32 bit)
Assigned to:		CPU Architecture:	Any
Tags:	Object Browser Schema fetching... Workbencch

Description:
I've been asked to raise my posting to the forums for Workbench as a bug by Mike Lischke. So, here goes:

I've just upgraded to the latest version of MySQL Workbench (5.2.38). However, when entering an SQL Editor screen, I find that the Object browser does not display my databases schemas, i.e. if I try to load one of the schemas, it simply displays as fetching and appears to hang. 

Any ideas? 

There is nothing in the server logs to explain this, and it didn't happen with the previous version of Workbench installed (5.2.35). 

Additional info: I'm running MySQL 5.1.51 Community Edition on a Windows 7 32-bit PC. Also, if I revert to the previous version, it won't load, so I'm stuck with the latest version with the problem described. 

How to repeat:
As described above: open Workbench, select a schema to query, and let the Object Browser open in an SQL Editor window. The selected schema simply remains in fetching... state. But the schema's tables can be queried.

If this is a bug, I found little references to it, but it sounds very similar to 60891.

Similar bug appears to be 64500.

Have since installed Workbench on a Windows 7 64 bit PC without incident. So what is the problem with the 32 bit version?

Are you sure server that you try to connect to works properly? Can you try to create new connection in 5.2.38 to the same server and check if it allows to see schemas?

I've just created a new connection and the same pattern occurs as per the older connections. The schema list appears but if I want to see the tables of a schema, everything remains in a fetching state. 

when I created the new connection, I tested it and the test was positive. queries can also run successfully. 

It is the schema list only that appears to be at fault.

Could this error be anything to do with the following at all? 

120309 8:04:57 [Note] Plugin 'FEDERATED' is disabled. 
120309 8:05:06 InnoDB: Started; log sequence number 2 166671137 
120309 8:05:14 [ERROR] Column count of mysql.db is wrong. Expected 22, found 20. The table is probably corrupted
 120309 8:05:14 [ERROR] mysql.user has no `Event_priv` column at position 29 
120309 8:05:14 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
 120309 8:05:14 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections.
 Version: '5.1.51-community-log' socket: '' port: 3306 MySQL Community Server (GPL)
 120309 8:42:17 [ERROR] Column count of mysql.proc is wrong. Expected 20, found 16. The table is probably corrupted
 
This is from file C:\ProgramData\MySQL\MySQL Server 5.1\data\Ustane.err where Ustane is the name of the C:\.

Looks like you have to run mysql_upgrade.exe on your server to fix problematic tables in the mysql database. Please, check if this helps.

Can you advise why I have to use mysql_upgrade.exe? I have not updated the database server on this PC at all? and if I do have to use it, where do I get it from and how do I use it?

Thanks.

I can't get mysql_upgrade to work via the Windows command line: it returns an admin error saying that I do not have admin rights. This is odd because I'm using the password for root?

Probably you need Administrator privileges at Windows OS level...

But I have admin rights on the PC in question.

Would an uninstall and then re-install of MySQL but with a newer version solve this problem.

Uninstalling 5.5.59 and replacing it with 5.1.62 worth a try in any case.

Do you mean uninstalling MySQL 5.1.51 and replacing it with a newer version?

Yes, I meant 5.1.51... We were not able to reproduce this internally on 5.1.59 and 5.1.61.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Have upgraded version of MySQL so bug is no longer relevant. Thanks.

Thanks for your report Martin.
I'm closing this defect due that the reporter has not been able to reproduce it after a MySQL Server upgrade.
Thanks.