topic Re: Problems Updating from 5.12 to 5.14 in Alfresco Archive

Problems Updating from 5.12 to 5.14

lpkchri1 — Wed, 22 Jan 2014 01:26:17 GMT

I am having a problem when upgrading from 5.12 to 5.14. I have a mySQL database, using Weblogic 12.1.1. When I deploy the activiti-explorer.war for 5.14 it appears to be attempting to run table creation scripts, rather than updating the existing tables. The schema update policy is set to true, an

Re: Problems Updating from 5.12 to 5.14

trademak — Wed, 22 Jan 2014 15:15:25 GMT

Hi,

The act_hi_identitylink table is created in the upgrade from Activiti 5.12 to 5.13. Are you sure no upgrade has been performed before (maybe manually). In an Activiti 5.12 database there should be no act_hi_identitylink table present.

Best regards,

Re: Problems Updating from 5.12 to 5.14

lpkchri1 — Wed, 22 Jan 2014 20:26:54 GMT

The problem appears to be that the schema.version does not get updated when the activiti-explorer updates the tables.

I have tried this several times, reverting the database back to 5.12 and what I am finding is that the first time I run the activiti-explorer after deploying, it runs successfully. I have verified that the act_hi_identidylink table gets created. But the act_ge_property table still shows the schema.version to be 5.12.

So as soon as I restart the server, I get the error above, as the activiti-explorer tries to re-create the database objects that already exist.

I noticed that the database scripts that are generated do not update the schema.version either, so it does not seem to be something I can fix by updating the database that way.

Can I just update the schema.version to 5.14 manually? What mechanism is supposed to update the version of the database?

Thanks for any help.

Re: Problems Updating from 5.12 to 5.14

trademak — Tue, 28 Jan 2014 09:49:36 GMT

The version should always get updated when you have database schema update set to true. Only when you execute the sql manually you won't get a version value. Are you sure you only used database schema update = true? Did you configure the Activiti Explorer to use a different database than the default in-memory H2 one?
If you used manual sql updates, then yes you can manually update the schema.version value if needed.

Best regards,

Re: Problems Updating from 5.12 to 5.14

lpkchri1 — Tue, 28 Jan 2014 19:22:54 GMT

I am using MySQL. I ended up using the manual sql update then updating the version.

Thanks!

Re: Problems Updating from 5.12 to 5.14

onlinesun — Mon, 24 Feb 2014 19:04:42 GMT

I'm having the same issue using Oracle. The first time after upgrading everything's fine, after restarting tomcat now I have the error "couldn't upgrade db schema: create table ACT_HI_IDENTITYLINK..". I did not manually upgrade anything, seems like the version did not get updated so it's still trying to do the upgrade (from 5.12.1 to 5.14).

Re: Problems Updating from 5.12 to 5.14

onlinesun — Mon, 24 Feb 2014 19:37:15 GMT

I checked the tables, in ACT_GE_PROPERTY, the version is still 5.12, even when I set databaseSchemaUpdate to true.
If I delete the table ACT_HI_IDENTITYLINK and try to run again, it's fine. But the database version never gets updated.

So, if I manually update the table ACT_GE_PROPERTY, what should be the value of schema.history? right now it's
create(5.11) upgrade(5.11->5.12)
After that I plan to set schema update to false, that might solve my problem, for now.

Re: Problems Updating from 5.12 to 5.14

jbarrez — Tue, 25 Feb 2014 09:33:40 GMT

If you execute the sql manually, you shouldn't care about the auto upgrade.
You can't mix the two approaches.

Re: Problems Updating from 5.12 to 5.14

gavnunns — Tue, 25 Feb 2014 13:11:11 GMT

I ran into the same issue when I upgraded myself. Turns out it was user error, for the exact reason Joram stated.

My preferred approach when I worked out what was wrong was to make sure the following auto update was set to false in my processEngineConfiguration. Then I ran the script update for my selected DB and it worked perfectly. I also prefer to have more control over schema updates so turning this off met my requirements anyway.

<code><property name="databaseSchemaUpdate" value="false" /></code>