Bug #95335 Error loading schema content after installing MySQL Workbench version 8.0.16
Submitted: 10 May 2019 20:15 Modified: 8 Aug 2019 19:25
Reporter: COREY COLLINS Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:8.0.16 OS:Windows (Server 2012 R2)
Assigned to: CPU Architecture:Other (x64)

[10 May 2019 20:15] COREY COLLINS
Description:
After upgrading from MySQL Workbench version 8.0.13 or 8.0.15 to version 8.0.16, I see the following output error when MySQL Workbench starts up: 

Error loading schema content
Error Code: 1146 Table 'performance_schema.user_variables_by_thread' doesn't exist

When selecting a table, I get the following errors:

Tables could not be fetched
Views could not be fetched
Stored Procedures could not be fetched
Functions could not be fetched

How to repeat:
Upgrade MySQL Workbench version 8.0.13 or 8.0.15 through the MySQL Installer or standalone download to version 8.0.16.

Suggested fix:
I do not get these errors when I revert to a version prior to 8.0.16.
[13 May 2019 9:08] MySQL Verification Team
Thank you for the bug report. I couldn't repeat this issue, please provide the my.ini of your server, which server version are you connecting.?
[13 May 2019 15:49] COREY COLLINS
The issue occurs on MySQL version 5.6.43 and 5.6.44.
[13 May 2019 16:18] MySQL Verification Team
Thank you for the feedback. Verified with server 5.6.44.
[13 May 2019 16:23] MySQL Verification Team
https://bugs.mysql.com/bug.php?id=95358 marked as duplicate of this one.
[16 May 2019 8:25] Jean-Louis Dupond
Hi,

Seems like that query was introduced in the following commit:
https://github.com/mysql/mysql-workbench/commit/1f9cb3ccf18385abb21aa224907fc230b1815c85
[17 May 2019 16:47] Christine Cole
Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 8.0.17 release, and here's the changelog entry:

On Windows, an error at startup prevented the successful fetching of
database objects for display in the Schemas tab.

Thank you for the bug report.
[26 May 2019 14:09] MySQL Verification Team
https://bugs.mysql.com/bug.php?id=95532 marked as duplicate of this one.
[9 Jul 2019 5:05] MySQL Verification Team
Bug #96129 marked as duplicate of this one
[5 Aug 2019 14:42] Olexandr Vynnychenko
Hi. Just upgraded to 8.0.17. Have exactly the same issue.

Version 8.0.17 build 14960816 (64 bits)
[8 Aug 2019 19:07] Guest User
NOT FIXED! Please re-open!
[8 Aug 2019 19:14] Guest User
I cannot find the fix in the Github so I think they forgot it for 8.0.17:
https://github.com/mysql/mysql-workbench/commits/8.0
[8 Aug 2019 19:25] COREY COLLINS
Issue not fixed in MySQL Workbench version 8.0.17 per the additional comments. Please re-open this issue.
[9 Aug 2019 7:33] Mike Lischke
The patch for this bug is here: https://github.com/mysql/mysql-workbench/commit/4e92d2d27e2e6a1ba8c0a3cf6bf96799bde8ecb8. It's a different bug number because we had found this problem internallly already a few days before it was reported here.

However, this is a twofold problem. One aspect is the version of the server where this table is supported. Another is that for user accounts that don't have the privilege to access the P_S, this will still fail. A fix for the latter problem has already been pushed and will be available with the next release of MySQL Workbench.
[9 Sep 2019 0:47] Jassim Rahma
I am having the same problem. 

I am using 8.0.17
[9 Sep 2019 13:08] Kevin Finkenbinder
Since this has not been reopened, I opened new issue at https://bugs.mysql.com/bug.php?id=96793 and referenced both this and https://bugs.mysql.com/bug.php?id=95228.