MySQL Bugs: #103570: Workbench stops working while copying data to target RDBMS, during migration

Bug #103570	Workbench stops working while copying data to target RDBMS, during migration
Submitted:	4 May 2021 11:27	Modified:	8 Jun 2021 13:00
Reporter:	Michel Asmar	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench: Migration	Severity:	S1 (Critical)
Version:	8.0	OS:	Windows (x64)
Assigned to:		CPU Architecture:	x86 (Corei7)
Tags:	bug, builk data transfer, crashes, freeze, migration, mysqlworkbench, not responding, RDBMS, stop working

Description:
every time i reach the "Bulk data transfer" step in the migration wizard process, MySQL Workbench stops working showing a "Not responding" message on the main window bar and a failed icon on the "Copying data to target RDBMS" step then the whole window turns plain white, and 2min later it turn plain black, i can't click on anything in the software before this happens to try to retrieve logs or anything because the software is frozen. Only thing i can do is kill the task in Task Manager and if i open the software again i have to repeat the whole migration process to reach this point again and get bugged.

I am migrating from SQL Server Management, all the previous steps were done correctly and successfully along with the connections.

How to repeat:
just startup the migration wizard from database tab in MySQL Workbench and do the process to migrate from SQL Server Management.

1

Attachment: cb684e57-9c4a-498a-8d6e-5d09e3da9cca.jpg (image/jpeg, text), 62.33 KiB.

below screenshots

Attachment: 82d617cf-19f4-400a-aa30-91bfae59d33f.jpg (image/jpeg, text), 8.76 KiB.

Hello Michel Asmar,

Thank you for the bug report.
May I please know the connection method used for connecting to server?

Regards,
Ashwini Patil

Hey, yes ofc
i am using ODBC data source

Hello Michel Asmar,

Are you using SSH to connect to source or target RDBMS?
Also, to investigate further this issue at our end, may I kindly request you to launch workbench under debug mode (-log-level=debug3) and provide unaltered workbench log file(more details about log are explained here - https://dev.mysql.com/doc/workbench/en/workbench-reporting-bugs.html). Thanks.

Regards,
Ashwini Patil

Hello Ashwini Patil

No, I am not using SSH to connect to the source or target RDBMS.
and running using debug didn't solve it, 
kindly find attached the latest log file

log file 6 May 2021

Attachment: wb.log (application/octet-stream, text), 284.46 KiB.

Hello Michel Asmar,

Thank you for the feedback.
I tried to reproduce your issue on windows 10 with workbench 8.0.25 but I am not seeing any issues at my end. 

Regards,
Ashwini Patil