MySQL Bugs: #76382: Database Migration

Bug #76382	Database Migration
Submitted:	19 Mar 2015 1:44	Modified:	18 May 2016 0:08
Reporter:	Jay S	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Migration	Severity:	S1 (Critical)
Version:	6.2.5	OS:	Linux (Ubuntu 14.04.2 LTS)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
I just wanted to let you know that you must have by mistake added the Database Migration menu option to mysql workbench. 

I understand this is the community edition - but it does not make any sense to add something that does not work as an available option. Thanks.

How to repeat:
1. Click Database Menu.

2. Choose options to migrate between MS SQL through iodbc datasource as source and MySQL stored connection as target.

3. After few seconds wait for workbench to become non responsive and go in to some sort of coma that it would never recover from.

Suggested fix:
Provide code contribution guidelines along these lines:

"At this time, we are only accepting python script contribution from developers who are at least ...?".

Thank you for your bug report. Could you attach wb.log and screetnshots that would help resolve that issue?

Update: I was able to get it working, but the workbench hanging is reproducible and happens only with the following:

1. If the selected source is using the freetds odbc driver, there is an option under the Advanced tab while we are at "Source RDBMS Connection Parameters"

2. If the option, "Driver sends Unicode data as UTF-8" is checked, (which is checked by default), even clicking Test Connection will cause the workbench to hang.

3. If it is not checked, it works fine.

Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 6.3.7 release, and here's the changelog entry:

The Driver sends Unicode data as UTF-8 advanced database migration option
that is available when using an ODBC driver is now disabled by default.
Also, connections could hang when this option was enabled.

Thank you for the bug report.