MySQL Bugs: #50491: Workbench Can't Fetch Schemas From MySQL 5.5

Bug #50491	Workbench Can't Fetch Schemas From MySQL 5.5
Submitted:	20 Jan 2010 22:23	Modified:	27 Jun 2011 14:56
Reporter:	Mikiya Okuno	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
Workbench cannot fetch schemas from MySQL 5.5 when using "Create EER Model from Existing Database" menu.

How to repeat:
Use "Create EER Model from Existing Database" menu and connect to MySQL Server 5.5.

Suggested fix:
n/a

Hi Mikiya,

we tried to reproduce the problem on our machines, but we're able to rev-eng. just fine from our 5.5 installations. what systems (os, arch) are you using - for workbench and the server machine (if not the same) . what exact server version are you running (we tried with current devel release here).
Can you connect to other MySQL hosts fine (if you have the chance to try)?

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".

I recently upgraded one of our Linux RHEL4 servers to MySQL 5.5.11. Ran the mysqlcheck --check-upgrade ... and all the databases checked out OK. However, I cannot fetch the tables through Windows Workbench 5.2.33 CE Revision 7508. I can see the remaining server Databases that are running MySQL 5.0 just fine. The one we upgraded, I cannot. The tables appear to be "fetching ...." on all the DB's except the information_schema. I am running Workbench on Windows XP SP3 on a Dell Optiplex 755 with 4 GB of memory.

The linux box is running Linux xxxxxx 2.6.9-89.33.1.ELsmp #1 SMP Mon Nov 15 19:02:30 EST 2010 x86_64 x86_64 x86_64 GNU/Linux

I have not upgraded any of our other linux boxes yet. Most of all our DB tables are MyISAM engines except for one table running INNODB. We typically run MySQL typically in a default configuration that comes straight out of the 5.5.11.. RPMs for RHEL4. We do not run MySQL as "root", but as another account. But all the servers running MySQL are setup in the same default configuration. So I can see all the older MySQL server's databases, but not the new one.

I have installed (as Complete) the latest Windows Workbench as it was doing the same thing with an earlier version of Workbench (it was still a 5.2 CE derivative). Didn't capture the entire version of the previous install.

I would like to resolve this issue as Workbench is a valuable tool.

Apparently, running the mysql_upgrade command fixed the issue.