Bug #69518 Import a dump fails
Submitted: 20 Jun 2013 1:08 Modified: 5 Nov 2015 14:29
Reporter: George Brooks Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S3 (Non-critical)
Version:6.3.5 OS:Windows (10, 32-bit)
Assigned to: CPU Architecture:Any

[20 Jun 2013 1:08] George Brooks
Description:
I did a dump of all non-MySQL schema then dropped all.  I then attempted to import the dump to recreate schema.  Import hung on the first script; exitcode 1 shown when Stop was clicked.

I was able to import usings all scripts from the command line, so no harm done.

George

How to repeat:
See above.
[21 Jun 2013 11:50] Chuck Bell
We need more information to diagnose and properly route the defect.

Is this a problem with Utilities (mysqldbexport/mysqldbimport) or Workbench proper?

Please provide more detail concerning the issue to include the commands and options used, and any particulars about the error message presented.
[21 Jun 2013 12:19] George Brooks
The error occurs in Workbench.  I reproduced the error this morning by opening a connection, clicking on Server, Data Export, and selecting all schema except mysql & performance_schema.  Export proceeded properly with 103 objects exported.  I then dropped 5 schema.  Clicked on Server, Data Import.  The process hung on the first script.  After clicking on Stop the following appears in the log window:

05:14:11 Restoring handsontahoe (contacts)

Running: "C:\Program Files\MySQL\MySQL Server 5.6\bin\mysql.exe" --defaults-extra-file="c:\users\george\appdata\local\temp\tmpbt2l4d.cnf"  --host=localhost --user=root --port=3306 --default-character-set=utf8 --comments < "G:\\Documents\\dumps\\Dump20130621\\handsontahoe_contacts.sql"

Operation failed with exitcode None

05:14:23 Aborted by User

Restored database(s) maybe in an inconsistent state
[14 Aug 2013 15:49] Chuck Bell
Reassigning category since this isn't a utilities defect.
[16 Aug 2013 11:22] Alfredo Kojima
What happens if you execute that command yourself from the command line?
[20 Aug 2013 18:06] George Brooks
I repeated the experiment today, which necessitated capturing the temporary file while the data import was hung up.  Contents of the temp file are:

[client]
password="thepassword"

In Workbench, the progress log hangs with :

10:54:05 Restoring handsontahoe (contacts)

Running: "C:\Program Files\MySQL\MySQL Server 5.6\bin\mysql.exe" --defaults-extra-file="c:\users\george\appdata\local\temp\tmpxb0kcv.cnf"  --host=127.0.0.1 --user=root --port=3306 --default-character-set=utf8 --comments < "G:\\Documents\\dumps\\Dump20130820\\handsontahoe_contacts.sql"

Operation failed with exitcode 1

10:55:54 Aborted by User

Restored database(s) maybe in an inconsistent state

At the command prompt, the identical command (once captured temp file was restored) succeeds.  This was confirmed by changing a record before running the command.

George
[5 Sep 2013 0:59] MySQL Verification Team
Please try version 6.0.7. Thanks.
[6 Sep 2013 3:26] George Brooks
Repeated experiment with Workbench 6.07.  It also hangs on first sql statement.  No change in behavior.

g
[23 Apr 2014 13:08] MySQL Verification Team
Please try version 6.1.4. Thanks.
[23 Apr 2014 22:03] George Brooks
I would like to be able to confirm this.  However...

After upgrading to Workbench 6.1.4 I attempted to perform an export and got the following:

WARNING
Error checking mysqldump version
Error retrieving version from mysqldump.exe:
The system cannot find the path specified.
mysqldump  Ver 10.13 Distrib 5.6.13, for Win32 (x86)
 (exit 1)

So I upgraded the server and workbench installation to the latest as of this date but the error persists.

The error persists after explicitly pointing to mysqldump.exe in Workbench's Edit>Prferences>Administrator screen.

I am less than amused.
[24 Apr 2014 13:44] George Brooks
I have resolved the export error - missing ansicon installation that prevented command prompt from behaving properly.  So I could perform an export successfully.

I cannot, however, import successfully.  Import hangs and when Stop is clicked the following appears:

06:34:20 Restoring projectmana (address)
Running: mysql.exe --defaults-file="c:\users\george\appdata\local\temp\tmpknfzh_.cnf"  --host=127.0.0.1 --user=root --port=3306 --default-character-set=utf8 --comments < "G:\\Documents\\dumps\\Dump20140424.sql"
Operation failed with exitcode 1
06:34:34 Aborted by User
Restored database(s) maybe in an inconsistent state
[26 Aug 2015 12:59] MySQL Verification Team
Please try version 6.3.4. Thanks.
[31 Aug 2015 22:27] George Brooks
After upgrading OS to Win10 I am unable to export data!  This remains true after upgrading Workbench to 6.3.4.  I've even stripped out all MySQL, cleaned up with CCleaner, and reinstalled server & workbench.  No change - no schema appear in Data Export window.

Attempting to import with a dump file created in Workbench 6.3.4 (on Win10 64-bit) results in the following:

Error executing task: [Error 5] Access is denied
Error executing task 'NoneType' object has no attribute 'stderr'

Still no joy.
[5 Nov 2015 10:53] MySQL Verification Team
Thank you for the feedback. Could you please provide the file for import test with 6.3.5. Thanks.
[5 Nov 2015 14:29] George Brooks
Export & import work appropriately.  The issue did not appear with 6.3.4; the  problem there was with the display in Windows 10.