Bug #69650 | MySQL to MySQL migration fails at db_mysql_fe_grt.py", line 137, in connect | ||
---|---|---|---|
Submitted: | 2 Jul 2013 16:24 | Modified: | 19 Nov 2013 19:27 |
Reporter: | Hegy Pascal | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: Migration | Severity: | S2 (Serious) |
Version: | 6.0.3 | OS: | Windows (7 SP1 x64) |
Assigned to: | CPU Architecture: | Any | |
Tags: | db_mysql_fe_grt.py, DbMySQLFE.connect |
[2 Jul 2013 16:24]
Hegy Pascal
[10 Jul 2013 13:01]
Hegy Pascal
Hello, Having the same issue with recent 6.0.3 version. Regards, Hegy Pascal
[12 Jul 2013 15:27]
Heiner Reinhardt
I am experiencing the same problem. The migration actually worked once. I tried different versions of the workbench (including 6.03, 5.2.42, 5.2.43, 5.2.47)
[22 Jul 2013 6:12]
A O
I have the same problem - I also see several other bugs that share a similar case of using SSH to connect to MySQL as the TARGET connection. In my case I'm going from MSSQL (WIN) to MySQL (Linux). Clicking the "Test Connection" button works. but once you get to to "Connecting to target" part or "Check target DBMS connection" it fails. I think the common thread is MySQL over SSH connections for the target.
[22 Jul 2013 14:51]
A O
I created a workaround by setting up an encrypted tunnel and doing MySQL target setup as if it was just a regular TCP (unencrypted) connection. It appears that the negotiated connection via the SSH component is the problem. I would hazzard a guess that the username USERNAME@127.0.0.1:3306@REMOTEIP:22 is not interpreted well by the program.
[23 Jul 2013 12:49]
Hegy Pascal
Yeah that's a great idea :) I will try this soon. Thanks for the tip. But I think this issue has to be fixed anyway. We are a lot who have this issue. Rgds, Pascal
[5 Aug 2013 18:23]
Sergio Andres De La Cruz Rodriguez
Posted by developer: Unfortunately, at this time we do not support source or target RDBMS connections through SSH. We are updating the error message to clearly state this. A workaround can be found in the comments by "A O" above.
[19 Nov 2013 19:27]
Philip Olson
This is now documented: + The migration process does not support source or target RDBMS + connections through SSH. + A workaround is to set up an encrypted tunnel, and then use the + MySQL target as if it is a standard TCP (unencrypted) + connection. Thank you for the bug report, and associated workaround.