MySQL Bugs: #83089: MYSQL Workbench 6.3.7 Crash With migration wizard

Bug #83089	MYSQL Workbench 6.3.7 Crash With migration wizard
Submitted:	22 Sep 2016 1:50	Modified:	18 Dec 2016 23:43
Reporter:	Han Wuoi	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Workbench: Migration	Severity:	S1 (Critical)
Version:	6.3.7/6.3.8	OS:	Windows (Win 7)
Assigned to:		CPU Architecture:	Any
Tags:	crash, migration, workbench

Description:
Using Migration wizard in workbench to migrate data from MS SQL 2012 Express edition.

All work well from setup ODBC connection to schema selection.

However after select source object, i only select 2 tables from the object and click next at the process of Preparing SQL the mysql workbench will immediate pop up a message indicates MYSQL Workbench stopped working and exit.

My DB is 8GB++, however i only select 2 tables which one is consist of 300k rows, and another is 9 million rows.

From the event log, its indicates the Exception code: 0xc0000005 and grt.dll

How to repeat:
1. Setup the source - localhost, ms sql, odbc native (tested connection)
2. Target - localhost, standard tcp / ip
3. select schema - tried with 2 tables from the object / all the tables
4. click next - the crash happened when the process to prepare the sql

Thank you for the bug report. Can you please run MySQL Workbench with --log-level=debug3 command line argument, repeat issues and then attach full log file (Help->Locate log fie)? Thanks

Attached wb log file

Event viewer log

Faulting application name: MySQLWorkbench.exe, version: 6.3.7.0, time stamp: 0x5758217b
Faulting module name: grt.dll, version: 0.0.0.0, time stamp: 0x5758165d
Exception code: 0xc0000005
Fault offset: 0x0000000000007674
Faulting process id: 0x1e08
Faulting application start time: 0x01d214e460fece22
Faulting application path: c:\Program Files\MySQL\MySQL Workbench 6.3 CE\MySQLWorkbench.exe
Faulting module path: C:\Program Files\MySQL\MySQL Workbench 6.3 CE\grt.dll
Report Id: c6291381-80d7-11e6-a204-642737d20cdc

Please provide the create table statement for SQL Server for both tables (private if you wish) or the file zipped of the database using the Files tab here. Thanks.

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'm getting a very similar crash, I get the error below.
Faulting application name: wbcopytables.exe, version: 0.0.0.0, time stamp: 0x5800cd76
Faulting module name: ntdll.dll, version: 10.0.14393.351, time stamp: 0x5801a332
Exception code: 0xc0000026
Fault offset: 0x00000000000a4830
Faulting process id: 0x2e0
Faulting application start time: 0x01d24fe0ac6f8ef0
Faulting application path: C:\Program Files\MySQL\MySQL Workbench 6.3 CE\wbcopytables.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 7e512bb7-9625-4856-b775-107137aa5ec9
Faulting package full name: 
Faulting package-relative application ID: 

I believe your team asked for the table creation statements, I'll see if i can get a copy of that in the next hour or so since I just kicked off a retry on the bulk data transfer.

Sorry, I'm also running off Windows Server 2016, with MySQL 5.7.16 and MySQLWorkbench 6.3.8.  Table creation scripts will be uploaded shortly.

I couldn't repeat with script provided:

Preparing...
Importing migration.sql...
Finished executing script
Operation completed successfully

and 6.3.8 WorkBench. If you get the issue with that script please provide the steps (would be nice with screenshots). Thanks.

Miguel,

I'm not sure what you mean about not being able to run the script.  That script is the output from the MySQL WorkBench Migration task.  I can see that all of the tables defined are created in my SPC schema by looking at the Target Results with the Migration Wizard.  Is it possible that the Wizard is not properly reading the source MSSQL database and inputting corrupted creation lines in the script?

Wait, I'm sorry I misread your original comment.  You were saying that you were unable to recreate the issue by running the table creation script.  Now I understand, I'm getting the crash during the Bulk Data Transfer, not during the creation.

Well in this case we need a script to create the SQL Server database or a small test database (zipped to attach here) so we can repeat the migration issue. Thanks.

Thank you for the feedback.

Can you confirm that issue on latest MySQL Workbench 6.3.9?