MySQL Bugs: #64778: Crash during import

Bug #64778	Crash during import
Submitted:	27 Mar 2012 13:53	Modified:	28 Mar 2012 13:34
Reporter:	Sergei Chaparin	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.38	OS:	Windows (Microsoft Windows Server 2008 R2 Standard Edition Service Pack 1 (build 7601), 64-bit)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
I was trying to import an SQL file with multiple databases into a test environment on a virtual Windows 2008 R2 server. MySQL workbench encountered a problem. 

How to repeat:
First export databases from the production environment, then open the file in the test environment.

Is it a big file? If yes this report is a duplicate, and not related to the environment details. There are already several reports with WB crash with files from a few dozens MB's and higher.

Peter
(not a MySQL person)

The file is a little over 50MB. The export was done in phpMyAdmin and the terminal using mysqldump --all-databases. The issue was caused by errors in the proc table of mysql database. Sorry I don't have error details.

What exact server version, 5.x.y, are you working with? Please, send the output of:

show create table mysql.proc;

(or show create table mysql.proc\G if you use mysql command line client)

from it.

I think it is randomly where it happens.  WB just cannot handle DUMPS of that size for import.  At least 4 similar reports exists.

Duplicate

MySQL version is 5.0.51a and the proc and procs_priv are actually empty. Thank you for your attention on this!

Hm, if you all know better... let it be a duplicate of Bug #55312, why not.

Sergei,

I'd say you should make sure your server is properly installed and all tables in mysql database have proper structure for the exact version used...