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:
None 
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
Description:
Below is the dump file which breaks the execution in this path - 

I have noticed this has BLOB datatype and  i suspect this is issue 

INSERT INTO `tablename` VALUES (2494,'%PDF-1.4\n%âãÏÓ\n3 0 obj <<
/Length 15408/Filter/FlateDecode>>stream\nxœµ]³ä¶q@ß÷WÌcRÅ;&¾Ro¶”XN,[±·*©<Œ­›Õvï*w÷Ú¥@wc« »9¨T%r¼«ÁàòðÞüæí·\\–Å_ÞþðæŸÞ¾ù·7öò/Çÿ×\\æýŽÿçùòöÛ_ý³¹{yû_oþáßþ÷ñgéÌ—¿~¨ÿ’w×ÍïÿÖp],þÝùø»sú/ïÞüÃo^nÏýñò‡Û‡Çãß7_ÞýÿNsùûþßüKùkúí›ÿøÏýÿþðÆl×pYârÙÿˆÝÒ?½óçÿ÷Ûùø#û_ùþ1„ý[>ÿëþëCþ×ÿmÿÿ?»qË5Úü×?R€Û•Ècè’—w\'¡g”.{~…€¯ ·s¼.öß¾||ýYNnç€äÖEÆœ/Õ¤/òò\n_A4í1^Mý_ŸxQLzô„ž±ÚS˜?yÒÓv\'=¿BÀWMºŸ¯Ký×ýü›—¿+¦Ý-Äûì壑§=MbwÚó+|û>í‹é°óòñ珯\nöHy·÷vÙcõ‘¬|¤|z	»Û¿&»_ó¿ýý囧O‘Ã;c~_Ÿzðå\rJð¥_^!à+Hà½YûÇûŸ¿×Ò{ãÞ3è½ñHŸþ¹K_^!à+ˆè£¹®[þ¿ÿ“‚|!ò0÷¿çË»“ÉùBäé$äaÞ®¶·¼ÿî÷ÿ®œ÷0Ó×]ýC¾¼C‰>³ôèË+|ýâûŸúßýþ;x Ã=l®èpÏ]ð@‡{z	ø2û«]»à¿ùwùf‘|ñsŸ<¿;™<qtÉó+|¹_»[º}q½½—£/ŽöñËÚßÍ–·\'¡gzy…€¯ B_ãuë}Ë}ÿòøóí—\nø•vuÑ™>üJ»ºŒÒ…_iW—^A]èŸÇüñ›Ë÷/OÏrøèf‚glëÊ”à3J','xls');

How to repeat:
same as above
[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".