Byte Order Mark added randomly with backups

Discussion of open issues, suggestions and bugs regarding database management and administration tools for MySQL
Post Reply
brezanac
Posts: 33
Joined: Thu 09 Jan 2014 14:52

Byte Order Mark added randomly with backups

Post by brezanac » Sun 23 Feb 2014 21:09

I am currently facing an issue where at random times backups would contain BOM (Byte Order Mark) which, of course, breaks the backup SQL script (dump). This prevents me from restoring those particular backups through dbForge (see attached picture) or even using them with any other mysql client. It is particularly troublesome for my automatic deployment workflows which break when trying to import dumps onto production servers.

The problem doesn't happen to often. I'd say once in every ten backups. And yes its not database specific since if I get a faulty backup (contains BOM) if I immediately repeat the process I'll get a dump without BOM. One additional information which might be of use is that I've noticed this behavior since the last two-three patches. It wasn't an issue before that.

dfForge 6.1.154
MySQL 5.5.35 (CentOS 6.5)

Image

Image

alexa

Re: Byte Order Mark added randomly with backups

Post by alexa » Tue 25 Feb 2014 11:34

Is it possible to send us the faulty backup script for investigation? You can upload it to our FTP server ftp://ftp.devart.com@anonymous

brezanac
Posts: 33
Joined: Thu 09 Jan 2014 14:52

Re: Byte Order Mark added randomly with backups

Post by brezanac » Thu 27 Mar 2014 13:47

alexa wrote:Is it possible to send us the faulty backup script for investigation? You can upload it to our FTP server ftp://ftp.devart.com@anonymous
Unfortunately the script contains information such as user data which I cant' share for obvious reasons.

However, recently I've noticed that its was not BOM that was causing the problem - it was two BOMs :D If you take a look at the attached picture you'll notice that there are two BOMs at the beginning of the dumped file, something I failed to notice with Sublime hex editor which was obviously showing inconsistent data.

So what essentially happens is that dbForge occasionally adds two BOMs at the beginning of a backup (dump) file which causes latter restore (execution) operations to fail because the first BOM is recognized as a legitimate byte sequence but the second one is not.

Image

alexa

Re: Byte Order Mark added randomly with backups

Post by alexa » Mon 28 Apr 2014 09:58

Could you please provide us a *.backup backup project file with your specific settings being generated in Database Backup Wizard?

Please also let us know what encoding you have specified in the 'Encoding' dropdown menu on the 'Advanced' tab of the Database Connection Properties dialog box (right-click the connection in Database Explorer and select 'Modify Connection...' from the popup menu)?

You can send a reply straight to our support system at supportATdevartDOTcom, so we will keep further correspondence with you via e-mail.

Post Reply