On 07/05/2014 16:40, Kevin Falcone wrote: > On Wed, May 07, 2014 at 12:51:07AM +0200, [email protected] wrote: >> used rt-serializer to dump the database, >> used rt-importer. > > Yeah - those are the relevant steps you didn't mention. > You're running into this bug I expect > http://issues.bestpractical.com/Ticket/Display.html?id=29158 > > -kevin
Yes that was the issue indeed and the posted SQL queries fixed it, thanks! With that out of the way we have found a new issue from the migration (hence the new subject): the attached files that were migrated are garbled. With that I mean: - TXT files are fine, even the charset is correct - ANY kind of file with binary in it (we tested jpg, pdf, doc, zip) appears to be corrupted. The plaintext bits of these files are identical (like a jpg has the plaintext string "JFIF" in its header), but everything else is completely messed up to the point where even the jpg header becomes invalid. I have attached 2 files (~40kb for both): -new from the migrated system and -old from the old system. The differences in a hex editor are pretty apparent, everything that's not plaintext is just wrong. Are there maybe any command line switches to rt-serializer and rt-importer that I missed? Thanks for the help!
-- RT Training - Dallas May 20-21 http://bestpractical.com/training
