Bug #56587 | mysqldump fails to dump database | ||
---|---|---|---|
Submitted: | 6 Sep 2010 10:13 | Modified: | 7 Oct 2010 12:50 |
Reporter: | Anil Alpati | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: mysqldump Command-line Client | Severity: | S1 (Critical) |
Version: | 5.1.45 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[6 Sep 2010 10:13]
Anil Alpati
[6 Sep 2010 10:23]
MySQL Verification Team
anil, this is why the --hex-blob option to mysqldump is useful. please, check if this will work better..
[6 Sep 2010 11:01]
Anil Alpati
Any comments
[6 Sep 2010 16:25]
Sveta Smirnova
Thank you for the report. Please send us what mysqldump command outputs while you are trying to restore the dump.
[7 Sep 2010 4:40]
Anil Alpati
Dump file which breaks in the middle.
Attachment: dump.sql.zip (application/zip, text), 504.55 KiB.
[7 Sep 2010 4:42]
Anil Alpati
Below is the command ./mysqldump -uroot -hhostname -ppassword --hex-blob jasperserver > "/media/disk/backups/jasperserver_`date`.sql"
[7 Sep 2010 12:50]
Sveta Smirnova
Thank you for the feedback. This looks like duplicate of bug #33048, but is interesting how you created invalid dump from such data. Please run queries: CREATE TABLE bug56587 LIKE jirepositorycache; ALTER TABLE bug56587 ENGINE=MyISAM; INSERT INTO bug56587 SELECT * FROM jirepositorycache; Then send us bug56587.MYD, bug56587.MYI and bug56587.frm files.
[7 Oct 2010 23: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".