MySQL Bugs: #65254: MySQL Fetching forever

Bug #65254	MySQL Fetching forever
Submitted:	9 May 2012 13:31	Modified:	13 Jun 2013 1:03
Reporter:	Dizzy Hunter	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	5.2.39	OS:	Windows (Microsoft Windows Server 2003, Enterprise Edition Service Pack 2 (build 3790))
Assigned to:	Juan Rene Ramirez Monarrez	CPU Architecture:	Any
Tags:	WBBugReporter

Description:
My workbench is stuck fetching tables forever

How to repeat:
Connect in databases with more then 4k of registers then click in one table to view

Thank you for the problem report.

The previous bug report of this type was resolved by running mysql upgrade tool.
This bug is happening only on a remote connection to the db. Local db connections are fine, and table names display instantly but the remote db stays "fetching.." mode forever.  Version 5.2.39 CE Revision 8557. Windows 7, 64bit. Same connection parameters another pc on the team using 5.2.35CD Revistion 7925 works fine!

So I downgraded to 5.2.35CD Revistion 7925 and now everything works fine!

Hi

I've been doing some testing using remote databases with both a huge number of tables and also tables with big records (many fields) and a huge number of records too.

I have not seen any unexpected behavior, this means the table information and the record selection is displayed at the end.

Regarding the record selection, if the fetch is limited, i.e. to 1000K rows the information is displayed in a reasonable amount of time, if the limit is removed then it takes a long time of course, but at the end the information is displayed too.

I tested this on 5.2.35, 5.2.39 and 5.2.42 with similar results.

Can you give it a try to the lastest version of WB and provide feedback about what you find?

Thanks in advance!

Hi!

I'm using the latest version of the Workbench (5.2.47 CE, Revision 10398)
I connect to a remote mySQL Server. After selecting a schema, no tables are fetched. Still "Tables fetching..." appears (for about 15 minutes now).
It is just a very small database (6 Tables, no data in them, abount 5 columns per table).
Views and routines ca not be fetched to.

I have exactly the same problem, with V5.2.42 and V5.2.47.

When I first installed workbench, table fetching worked.  I don't remember what version I started on.  I don't know whether I've done something in the database that triggered this problem.

The database is MySQL 5.5.29-0ubuntu0.12.10.1 running on Ubuntu 12.10.  I have root access on this machine, so if you can tell me how to generate diagnostic information that might help track this down, I'm happy to oblige.

The client is Windows 7.  The client and server are on a local 1GB network.

I am currently using MySQL Query Browser 1.2.12, which works fine.  Table fetching is instant.

I can open the log file in Workbench in Windows.  The log file ends with this message:

09:36:22 [INF][      Workbench]: UI is up
09:36:23 [INF][      Workbench]: Running the application
09:36:30 [INF][     SSH tunnel]: Starting tunnel
09:36:31 [INF][        WQE.net]: Launching SQL IDE
09:36:33 [ERR][            grt]: Error Code: 1548
Cannot load from mysql.proc. The table is probably corrupted	Get schema contents

/var/lib/mysql/mysql.proc does not exist on the server.  "locate mysql.proc" returns nothing, so there is no mysql.proc anywhere on the server.  Can this be reconstructed somehow, or is the error unrelated?

The only other error in the Workbench log is the very first line:
09:36:20 [ERR][      Workbench]: Console redirection failed.

This is solved by running mysql_upgrade on the server:

$ mysql_upgrade -p -u root
Enter password:

Fixed as of the upcoming MySQL Workbench 6.0.2 public beta release, and here's the changelog entry:

Instead of freezing at "Tables fetching..." when table records could not
be fetched, MySQL Workbench will now report this issue by updating the
associated fetch icon and report it as "Could not be fetched".

Thank you for the bug report.

This bug is triggered as well in linux machines.

I am able to reproduce it as Fedora have changed the mysql package to install mariadb and on an update my mysql installation got wiped and mariadb installed instead.

This bug got triggered and fixed as explained with mysql_upgrade.

I went ahead on my work until i logged using the mysql command line utility when I saw the mariadb prompt.

Then I realized my mysql installation was removed but the databases got in the same place and was being served by mariadb.

When I reverted back to mysql, I logged with the mysql command line again and and any query to the  information_schema.routines table ended up with:

ERROR 1548 (HY000): Cannot load from mysql.proc. The table is probably corrupted

Using mysql_upgrade fixed it up again.