Bug #93228 | Database unusable after crash during export | ||
---|---|---|---|
Submitted: | 16 Nov 2018 12:07 | Modified: | 16 Dec 2018 13:57 |
Reporter: | Malcolm Sparrow | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench: Administration | Severity: | S1 (Critical) |
Version: | 8.0.12 | OS: | MacOS (High Sierra & Mojave) |
Assigned to: | CPU Architecture: | Any | |
Tags: | Backup, corruption, crash, data loss, export |
[16 Nov 2018 12:07]
Malcolm Sparrow
[16 Nov 2018 12:10]
Malcolm Sparrow
MySQL error log
Attachment: error-log.txt (text/plain), 45.43 KiB.
[16 Nov 2018 12:12]
Malcolm Sparrow
Further - a subsequent export has resulted in no crash, but a total failure to export due to being unable to connect to the server (despite currently being connected). Please see the attached 'export-failure.txt'
[16 Nov 2018 12:12]
Malcolm Sparrow
Export failure output...
Attachment: export-failure.txt (text/plain), 1.79 KiB.
[16 Nov 2018 13:57]
MySQL Verification Team
Thank you for the bug report. Please try version 8.0.13 if the issue still exists we need a backup file the smaller possible to run the test, zip the file and attach using the Files tab with private option. Thanks.
[17 Dec 2018 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".