Bug #66611 | Error "the command line is too long" when migrating 500+ tables | ||
---|---|---|---|
Submitted: | 30 Aug 2012 12:13 | Modified: | 15 Jan 2013 23:11 |
Reporter: | Tom De Puysseleyr | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: Migration | Severity: | S2 (Serious) |
Version: | 5.2.42 | OS: | Windows (Microsoft Windows 7 Service Pack 1 (build 7601), 32-bit) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
[30 Aug 2012 12:13]
Tom De Puysseleyr
[30 Aug 2012 13:23]
MySQL Verification Team
Thank you for the bug report. Looks duplicate with http://bugs.mysql.com/bug.php?id=66516 please check. Thanks.
[30 Aug 2012 13:37]
Tom De Puysseleyr
Not sure if it's the same. On the screenshot, the "bulk data transfer" is empty, while in my case it starts the transfer and aborts with an error. I'll attach a screenshot and a copy/paste of the complete message log on that screen.
[30 Aug 2012 22:22]
MySQL Verification Team
http://bugs.mysql.com/bug.php?id=66628 marked as duplicate of this one.
[15 Jan 2013 23:11]
Philip Olson
Fixed as of the upcoming MySQL Workbench 5.2.46, and here's the changelog entry: The "Bulk Data Transfer" migration step would fail if too many tables were being migrated, because too many arguments were being passed to the command-line. This table listing is now saved to a new file named "wb_tables_to_migrate.txt", which is now read during the migration process. Thank you for the bug report.