Activities storetype changed! – Migration from Connections 4 to 4.5

I just upgraded our Connections environment from 4 to 4.5. Unfortunately it didn’t run as smoothly as expected.

I did a side-by-side migration (no application artifacts export) and copied all content stores to the new server

A really nasty problem was that all activities file uploads could not be accessed after the upgrade 🙁

So I checked logs and the DB tables and found out that the storetype of activities uploads changed from filesystem to filestore

-> everytime I tried to download pre-migration files Connections did a lookup for the storetype filesystem which was not defined in oa-config.xml

Fixup was easy, just change the storetype in oa-config.xml to filesystem

Screen 2013-04-25 at 15.42.39

If you uploaded files to activities after migration but before changing oa-config.xml you have to define a second storetype in oa-config.xml or you can go to your DB2 server and change the field STORETYPE of all new files in table ACTIVITIES.OA_CONTENTREF to filesystem.

 

Comments

Jared
Reply

Good post – is there any good resources (apart from the wiki) on doing a side-by-side migration of Connections from v4.0 to v4.5 ?
thanks

rakesh
Reply

Thanks for sharing . Could you please share us doc for IBM connection migration 4.5 ?

Michael Urspringer
Reply

Thanks Klaus. That was a problem I struggled with for days here 🙁 I would have said that someone should already have seen this in migration scenarios? You seem to be the only one so far?

Klaus Bild
Reply

Looks like, yes, or everyone found my blog for the solution 😉

Michael Urspringer
Reply

It seems so 😉 Did you ever open a PMR for that? Otherwise I will do that. It needs to be officially documented.

Klaus Bild
Reply

No PMR, you have to create one, thx

Michael Urspringer
Reply

Great. Could you please tell me the PMR number?

Nacho (@nachoenjuto)
Reply

Hey guys, it worked to me as well!! thanks a lot for the comments.
One more thing, as I was migrating from 3.0.1, mystoretype had the name of “contentstore” in the database. I added a new storetype called “contentstore” and it worked

byee

Leave a Reply

%d bloggers like this: