topic MySQL Migration Activiti Errors in Alfresco Archive

MySQL Migration Activiti Errors

clperkins — Thu, 16 Aug 2012 17:34:28 GMT

I am in the process of migrating our Alfresco from it's default Postgres DB to MySQL. If I could avoid doing so I definitely would but our development team has standardized on MySQL. Here is a brief overview of my migration strategy:1.Dump PG DB using –column-inserts –data-only options.2.Create a ne

Re: MySQL Migration Activiti Errors

afaust — Thu, 16 Aug 2012 20:34:48 GMT

Hello,

1) Index has nothing to do with Activiti process definition persistence, so a re-index would not help at all.
2) I don't see any values that look like alf_data directory structures.
3) I assume your migration has left the XML data somewhat mangled. Those "\012" look a bit suspicious and should probably not be there. I'd think they are the result of dumping the byte data from postgres into a text-based file.

Unfortunately, I am not familiar with Postgres to MySQL migrations, so I can't give any tips on this. But I would try to attempt another migration with proper care for the byte columns…

Regards
Axel

Re: MySQL Migration Activiti Errors

clperkins — Thu, 16 Aug 2012 20:44:52 GMT

Yeah, after thinking about what I said I realized I was reaching a bit on the re-indexing part.

I'll keep looking, thanks.

Re: MySQL Migration Activiti Errors

deas0815 — Thu, 13 Sep 2012 13:30:16 GMT

Hm … this one looks familiar to me.

The short story is that pg2mysql does not properly deal with binary data. The fix is to replace '\x…' or '\\x…' with unhex(‘…’) for mysql. You can find more details at http://www.contentreich.de/migrating-alfresco-from-postgresql-to-mysql

regards
Andreas

Re: MySQL Migration Activiti Errors

mrogers — Thu, 13 Sep 2012 14:54:58 GMT

There's another thread somewhere in these forums with the same issue which relates to the character set uses for textual data. Its important that the input and output match. The good news is from what I remember of that issue it got fixed!