MySQL Bugs: #73489: mysqldump Version Mismatch

Bug #73489	mysqldump Version Mismatch
Submitted:	6 Aug 2014 20:08	Modified:	22 Aug 2014 16:34
Reporter:	Patrick Moody	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S2 (Serious)
Version:	6.1.7	OS:	Windows (2007 R2 )
Assigned to:		CPU Architecture:	Any
Tags:	mismatch, mysqldump, version

Description:
I installed 5.7.4 and successfully migrated a database from 5.1.23. I was able to migrate the data successfully and the application was migrated to the new database and all is well and functioning.

Using the installer for 5.7 I checked the option for all the tools and apps.

Then I decided to figure out how to backup the database and could only find the Export functions and could not find a backup option as with previous versions of the administration tool.

When I attempted to export the database I get the below error.

"mysqldump Version Mismatch

mysqldump.exe is version 5.6.17, but the MySQL Server to be dumped has version 5.7.4-m14-log.
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 of the dump tool must then be set in Preferences -> Administrator -> PAth to mysqldump tool:"

2 Question

1. Does this error mater? If so, do you have a proper version of mysqldump?
2. How do I setup a daily automatic backup like the previous 5.1 version?

How to repeat:
Try to export a database using export feature on MySQL 5.7.4

Suggested fix:
Provide correct version of client tools

Screen shot of error

Attachment: Mysqldump error.jpg (image/jpeg, text), 52.93 KiB.

Thank you for the report.
Verified as described.

WARNING
mysqldump.exe is version 5.6.19, but the MySQL Server to be dumped has version 5.7.4-m14-log.
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:
16:29:52 Dumping test (t1)
Running: mysqldump.exe ***** has finished

Workaround:

I think MySQL workbench is using the bundled mysqldump(In 6.1.7, I think it 5.6.19 or so), you can just point it to use 5.7.4's mysqldump to use instead of default bundled

Edit->Preferences->Administrator<TAB>
Selected path to mysql dump tool: <path to 5.7.4>/bin/mysqldump.exe

Confirm this by cliking "Ok" and reopen the WB and try to dump.

See Bug #68328

Error using 5.7.4 mysqldump

Attachment: Mysqldump error.jpg (image/jpeg, text), 52.93 KiB.

Bundled mysqldump version

Attachment: file.jpg (image/jpeg, text), 29.56 KiB.

I tried that after I sent in this support request. That didn't work, workbench script doesn't work with the newer version of mysqldump.exe that is included in the workbench bundle.

Looks like something was overlooked on this version of workbench.

The screenshot you pasted for the error while supposedly using mysqldump from 5.7.4 says it's still using the bundled mysqldump. Please check that the path specified in the mysqldump path preference option is correct and exists.

BTW MySQL 5.7.4 is still under early development and should not be used for production use unless you're fully aware of all the risks involved. The current production ready version of MySQL is the 5.6 series.

This is not really a bug, WB bundles mysqldump for the latest GA version of MySQL, but you're running an alpha version. In that case, you have to set the option to pick a custom mysqldump executable to select the same mysqldump that came with your server.

I had same problem. What works for me is as below
I copied mysqldump.exe from mysql server to workbench folder (respective folder at destination)

Thanks Vinil!!  I had same problem and this worked for me!!