Bug #93983 source-timeout parameter requested but none
Submitted: 18 Jan 2019 15:01 Modified: 8 May 2020 12:06
Reporter: Timothee BARON Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Migration Severity:S1 (Critical)
Version:8.0.13 OS:Ubuntu
Assigned to: MySQL Verification Team CPU Architecture:x86
Tags: source-timeout

[18 Jan 2019 15:01] Timothee BARON
Description:
Hi,

The tool is not able to find the parameter source-timeout while execution the data migration:
######
/usr/lib/mysql-workbench/wbcopytables-bin: Invalid option --source-timeout=

ERROR: Determine number of rows to copy: Error getting row count from source tables, wbcopytables exited with code 1
Failed
######

So I'm stuck at the stage "Bulk Data Transfer" and the tool remain unusable.

Thank you in advance for your help.

Timothee

How to repeat:
Just launch any migration from mysql workbench

Suggested fix:
None
[18 Jan 2019 15:22] Timothee BARON
Changed from Debian to Ubuntu
[18 Jan 2019 15:41] MySQL Verification Team
Thank you for the bug report. I couldn't repeat this issue on Ubuntu 18.04, could you please provide screenshots of each step you does. Thank in advance.
[18 Jan 2019 16:07] Timothee BARON
Hi,

I just clicked on Next in each steps in the migration Wizard. Could also connect with source and target databases.

Cheers,
Timothee
[18 Jan 2019 18:17] MySQL Verification Team
Thank you for the feedback. I tried a migration from a MySQL 8.0.13 server data running on Ubuntu 18.04 to MysQL source build 8.0.14 running on Manjaro, which kind of migration failed on your side. Thanks.
[21 Jan 2019 9:44] Timothee BARON
Hi,

I am migrating a database from MS SQL 2017 to MySQL 5.5 using FreeTDS.

Regards,
Tim
[23 Jan 2019 12:00] MySQL Verification Team
Thank you for the feedback. Server 5.5.XX isn't supported by WorkBench 8.0.13.
https://www.mysql.com/support/supportedplatforms/workbench.html
MySQL Workbench 8.0 is the current release and is recommended for MySQL 8.0. It also works with MySQL 5.6, 5.7.
[23 Jan 2019 17:35] Timothee BARON
Hi,

Sorry I mistyped the version, it is actually:
mysqld  Ver 5.7.24-0ubuntu0.18.04.1 for Linux on x86_64 ((Ubuntu))

And actually, I'm not sure the version of MySQL would be involved in this error... Is a missing parameter "source-timeout" for the binary command "/usr/lib/mysql-workbench/wbcopytables-bin" would cause the error because of a particular version of MySQL? Sorry I don't see the link between them.

Is there any fix for this empty parameter?

Thank you,
Timothee
[31 Jan 2019 16:41] Timothee BARON
Please could you change the status of the ticket from unsupported to open as the version of MySQL is supported as per your comments.

Thank you,
Timothee
[19 Feb 2019 23:54] MySQL Verification Team
Thank you for the feedback. Are you able to provide a sql script for SQL Server with create table and enough insert so we could try to create it with SQL Server and then to test the migration?. Thanks.
[20 Mar 2019 1:00] Bugs System
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".
[14 Feb 2020 5:00] MySQL Verification Team
Am able to repeat on Linux Mint using 8.0.19 to migrate MSSQL to MySQL.
[14 Feb 2020 5:15] MySQL Verification Team
Check if you have both mysql-workbench (6.3) and mysql-workbench-community (8.0) installed. Removing the old mysql-workbench resolved the issue for me.
[8 Apr 2020 12:06] MySQL Verification Team
Thank you for the feedback.
Please could you follow as suggested by my senior Scott and get back to us if you still have this issue. Thank you.
[9 May 2020 1:00] Bugs System
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".
[19 Aug 2020 18:35] Jorge Morales
This is rather old and reported for a previous version, but; Can confirm. This was happening to me on Ubuntu 18.04 with MySQL Workbench 8.0.21 while migrating a MySQL 5.7 to MySQL 8.0.

Following recommendation, I checked, and yes; I had v6.x installed also. Once I removed that old version of MySQL Workbench, the migration followed through with no problems.