MySQL Bugs: #34538: Could not fetch schema table status

Bug #34538	Could not fetch schema table status
Submitted:	14 Feb 2008 9:52	Modified:	16 Oct 2008 12:21
Reporter:	Hans-Joachim Ballin	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Administrator	Severity:	S2 (Serious)
Version:	5.0-r12	OS:	Windows (XP-SP2-DE)
Assigned to:		CPU Architecture:	Any
Tags:	administrator, fetch, schema

Description:
Current configuration:
-Windows XP-SP2-DE
-GUI: mysql-gui-tools-5.0-r12-win32
-Server: mysql-essential-5.0.51a-win32
-ODBC: mysql-connector-odbc-5.1.1-win32
-.NET: mysql-connector-net-5.1.4
######################################################
Get grant info for the user I'm using...
mysql> SHOW GRANTS FOR root@localhost;
+----------------------------------------------------------------------------------------------------------------------------------------+
| Grants for root@localhost                                                         |
+----------------------------------------------------------------------------------------------------------------------------------------+
| GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost' IDENTIFIED BY PASSWORD '*E34D90F1EA7153F369DF97F544FAA0A54F27D7F0' WITH GRANT OPTION |
+----------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

mysql>
######################################################

I'm using just one schema with about 62 tables.

How to repeat:
o open Admin Tool and logon with privileged user --- using root.
o select schema "mysql"...works fine
o select my own schema...getting error message: "could not fetch schema table status."
o select schema "mysql" again...also getting same error message: "could not fetch schema table status."

o reconnect Admin Tool..have same error message
o Restarting DB server and connect via Admin Tool...works fine for schema "mysql"
o select my own schema...getting same error message again: "could not fetch schema table status."

I found this info in bug report #28140
#################
I was receiving the same message running MySQL on Windows Server 2003 and McAfee.  To test this, I turned the McAfee anti-virus off and tried to show the schema.  It worked every time.  I am writing McAfee to see how to make the scanning less agressive on the MySQL directories.
#################

It seems to be this is the issue. Well, is there any timeout parameter to tune this circumtance?

-Hans

I have McAFee 8.5i installed on my PC. If I stop this service "McAFee McShield" I never got this error message again.
Is someone experienced in tuning McAFee in case of tolerate MySQL environment.

-Hans

Now I have the resolution for ths specific problem + McAFee...

Resolution:
1. Open  "VirusScan Console"
2. Select Task [Access Scanner]
3. Select [Properties]
4. Select [Dedection]
5. In group [What to scan] change from option [All files] to [Default + additional file types] and check the option [Also scan for macros in all files]
6. Select [Apply]

Hi I got the same problem "Can not fetch schema table status". I was able to resolve the issue by excluding the mySQL directory and all subfolders from the directories Mcafee monitors for the on-access scan. 

The funny thing is that i had been running for the last 3 months with out a problem. I added a table to my schema and that is when i started getting the problem. 

In addition to not being able to use the MySQL Administrator I was also getting problems in Visual Studio 2005, when connecting via the .Net connector ver 5.2.1, this also went away after the fix. The error here was "Can't create/write to file" with err 17

I am using: 
Mcafee VirusScan Enterprise 8.5.0i, 
scan engine: 5200.2160,
Dat version 5236.0000 created on Feb 22, 2008.
MySQL version: 5.0.45-comunity-nt and 
MySQL Adminstrator version: 1.2.12
Windows XP service pack 2

thanks, Stevenson Gossage

Thank you for the bug report. I couldn't repeat the behavior reported. Are you able to do the expected behavior using the mysql.exe client?. Thanks in advance.

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