Bug #59411 mysqldump failure when exporting
Submitted: 11 Jan 2011 6:14 Modified: 7 Feb 2011 15:26
Reporter: Sidney van de Stouwe Email Updates:
Status: Closed Impact on me:
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.31 CE OS:Windows (window 7 64 bit)
Assigned to: CPU Architecture:Any

[11 Jan 2011 6:14] Sidney van de Stouwe
USING the mysqldump.exe from the server package
08:07:06 Dumping surface_master_flow_data (t_surface_flow_00)

Running: "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqldump.exe" --defaults-extra-file="d:\users\sidney~1\appdata\local\temp\tmpfg0uy2"  --no-create-info=FALSE --order-by-primary=FALSE --force=FALSE --no-data=FALSE --tz-utc=TRUE --flush-privileges=FALSE --compress=FALSE --replace=FALSE --host=localhost --insert-ignore=FALSE --extended-insert=TRUE --user=root --quote-names=TRUE --hex-blob=FALSE --complete-insert=FALSE --add-locks=TRUE --port=3306 --disable-keys=TRUE --delayed-insert=FALSE --create-options=TRUE --delete-master-logs=FALSE --comments=TRUE --default-character-set=utf8 --max_allowed_packet=1G --flush-logs=FALSE --dump-date=TRUE --lock-tables=TRUE --allow-keywords=FALSE --events=FALSE "surface_master_flow_data" "t_surface_flow_00"

Operation failed with exitcode -1073741819

08:07:11 Export of d:\Users\Sidney van de Stouwe\Documents\dumps\Dump20110111-15 has finished with 1 errors

USING the mysqldump.exe included in the workbench

mysqldump.exe is version 5.1.40, but the MySQL Server to be dumped has version 5.5.8.

Because the version of mysqldump is older than the server, some features may not be backed up properly.

It is recommended you upgrade your local MySQL client programs, including mysqldump to a version equal to or newer than that of the target server.

The path to the dump tool must then be set in Preferences -> Administrator -> Path to mysqldump Tool:

08:04:58 Dumping surface_master_flow_data (t_surface_flow_00)

Running: "mysqldump.exe" --defaults-extra-file="d:\users\sidney~1\appdata\local\temp\tmpxpxj32"  --no-create-info=FALSE --order-by-primary=FALSE --force=FALSE --no-data=FALSE --tz-utc=TRUE --flush-privileges=FALSE --compress=FALSE --replace=FALSE --host=localhost --insert-ignore=FALSE --extended-insert=TRUE --user=root --quote-names=TRUE --hex-blob=FALSE --complete-insert=FALSE --add-locks=TRUE --port=3306 --disable-keys=TRUE --delayed-insert=FALSE --create-options=TRUE --delete-master-logs=FALSE --comments=TRUE --default-character-set=utf8 --max_allowed_packet=1G --flush-logs=FALSE --dump-date=TRUE --lock-tables=TRUE --allow-keywords=FALSE --events=FALSE "surface_master_flow_data" "t_surface_flow_00"

08:05:00 Export of d:\Users\Sidney van de Stouwe\Documents\dumps\Dump20110111-14 has finished

How to repeat:
Workbench version 5.2.31 CE
MySql Version = 5.5.8

1. system disk is C:
2. User accounts are on D:\users
3. workbench and mysql server are installed on c:
4. workbench preferences-administrator mysldump location to mysql server bin directory
5. export any data to the default dump directory causinf the described error

Suggested fix:
For now use the mysqldump.exe included in the workbench suite
[11 Jan 2011 6:42] Sidney van de Stouwe
Just did some more checking and it apprears that it is caused by the location of  --defaults-extra-file="d:\users\sidney~1\appdata\local\temp\tmpkeiszm". If I copy the log output to a mysqldump commandline it also failes. If I replace the extra file with --user=root --password=xxxxx it works fine.

I therefore suspect that using the extra-file option has an error if the users directory is on a different drive then where the mysqldump.exe is residing

I have tested the same output on a different computer where user directory is on the same drive as where mysqldump.exe is.
[11 Jan 2011 9:05] Peter Laursen
59401 looks similar

(not a MySQL person)
[1 Feb 2011 13:11] Johannes Taxacher
This is a result of a bug in mysqldump (Bug #59234) - we have added a workaround to workbench repository.
[7 Feb 2011 15:26] Tony Bedford
An entry has been added to the 5.2.32 changelog:

Running the version of mysqldump supplied with the MySQL Server package resulted in the following error:

Operation failed with exitcode -1073741819