Upgrade to 3.2 Community from 3.0D fails on Authorities

warren_mcdonald — Sat, 25 Sep 2010 01:00:19 GMT

Hello,During testing the upgrade process from 3.0D to 3.2 the MySQL schema operations execute successfully and all of the patches up to the Authority Migrations work as well. The authority migrations ran for 12 hours and the failed with the following error. org.alfresco.error.AlfrescoRuntimeExcepti

Re: Upgrade to 3.2 Community from 3.0D fails on Authorities

warren_mcdonald — Tue, 09 Nov 2010 11:02:19 GMT

Hi,

this was solved by up grading from 3.0D to 3.3g. There was some chatter about several improvements to upgrade scripts in later versions, so i bit the bullet and went further on up the releases. I assumed, perhaps luckily, that being the most mature 3.3 it would offer the best chance.

Several issues were encountered in the upgrade:

It was essentially self dependent on two counts.

Indexes
I deleted all indexes, so the first run rebuilt indexes, but only some. I got an error saying that indexes did not exist for all stores. On restart it rebuilt indexes again (Index mode set to FULL) but this time did them all. I put this down to WCM not being fully initialized into the code base on the first run. I suppose this could be avoided by getting the application modules and config up to required standard on a temp repo and db, and then reconfiguring to switch to the live copies.

Missing nodes (perhaps indexes again)
After successfully proceeding through SQL scripts and most repo patches, some failed with errors on missing nodes.
After a shutdown and restart (also rebuilding indexes) the previously failed repo patches completed successfully.
Seems like this may be due to missing index entries for changes made during earlier upgrade patches.

Also
LDAP Sync
The first LDAP Sync is a full one as the Auth registry setup is different in 3.3. Including new zones. This took a long time for 23000 users.
Also a gotcha in there. In the new LDAP config you can specify which LDAP users should be treated as Admins. This somehow affects the zones and since our admins were also Share site managers we ended up losing control of most of our Share sites. i.e. they were not in the right APP auth zone. Some script trickery by a friendly local expert allowed us to hack the required Manager role assignments back in.

Anyway, after many, many hours of tests and reruns we finally have a migrated and repo. Without any help from community or Alfresco watchers.

Cheers,

Warren

topic Re: Upgrade to 3.2 Community from 3.0D fails on Authorities in Alfresco Archive

Upgrade to 3.2 Community from 3.0D fails on Authorities

Re: Upgrade to 3.2 Community from 3.0D fails on Authorities