Bug #101245 I can,t export database
Submitted: 20 Oct 2020 15:03 Modified: 23 Nov 2020 10:47
Reporter: Alberto Nico Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:8.0.20 OS:Windows (Microsoft Windows 7 Home Premium Service Pack 1)
Assigned to: MySQL Verification Team CPU Architecture:Any
Tags: WBBugReporter

[20 Oct 2020 15:03] Alberto Nico
Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\lacio\AppData\Roaming\MySQL\Workbench\log\wb.log]

I get the following message:
11:23:14 Dumping cr29_v01 (avw_v0)
Running: mysqldump.exe --defaults-file="c:\users\lacio\appdata\local\temp\tmpywovtx.cnf"  --user=lacio --host=localhost --protocol=tcp --port=3306 --default-character-set=utf8 --skip-triggers "cr29_v01" "avw_v0"
mysqldump: Couldn't execute '/*!80000 SET SESSION information_schema_stats_expiry=0 */': Unknown system variable 'information_schema_stats_expiry' (1193)

Operation failed with exitcode 2
11:23:16 Export of I:\CRD19\Tablas Importadas (1) has finished with 1 errors

I tray in many ways and couldn,t export any table. Also Y canĀ“t ony set  variable information_schema_stats_expiry. I get the message that it does not 
exist

How to repeat:
Any time I try to export a schema it appears
[20 Oct 2020 15:04] Alberto Nico
log file

Attachment: wb.1.log (application/octet-stream, text), 10.23 KiB.

[23 Oct 2020 10:47] MySQL Verification Team
Hello Alberto Nico,

Thank you for the bug report.
Imho the error is due to mysqldump version mismatch.
Please try below workaround.

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

Confirm this by clicking "OK" and reopen the WB and try to export.

Regards,
Ashwini Patil
[24 Nov 2020 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".