Database upgrade script for 5.13 doesn't alter schema.version table

[tiesebarrell]

When examining the upgrade scripts for the 5.13 release, I noticed the schema.property row in the ACT_GE_PROPERTY table is not upgraded. There is only one update to the schema, an additional history table. Is the omission of the update to the ACT_GE_PROPERTY table intentional?

We can't use the automatic upgrade mechanism of the engine and are reliant on the scripts for database schema migration. I had expected the scripts to be ready for autonomous use, but judging by the current scripts, they are not. Do I need to create my own additions to the script?

[tiesebarrell]

I have added the following to the script (Oracle). Can someone confirm this is all that's required? It appears to work correctly with the 5.13 engine.

<code>
update ACT_GE_PROPERTY set VALUE_ = '5.13' where NAME_ = 'schema.version';
update ACT_GE_PROPERTY set VALUE_ =
(select VALUE_ || ' upgrade(5.12 -> 5.13)' FROM ACT_GE_PROPERTY where NAME_ = 'schema.history')
where NAME_ = 'schema.history';
</code>

[jbarrez]

Hmm that indeed seems to be an error from our part.

The auto upgrade indeed sets the property correctly.
The script approach should do the same, but it does not.
You are right, you need to apply that sql manual or else your engine won't reboot.

The problem is that we ca't fix it retro-actively…. in theory if we add the same for the 5.14 (or 5.13.1) it should just work.

[tiesebarrell]

Hi Joram,

OK, thanks for the confirmation. At least it's now documented here for people to find if they need it.

[frederikherema1]

Thanks for sharing, Tiese

[ambharath]

In activiti-explorer (ver 5.13), inside the activiti-engine-5.13 jar file, I don't see any upgrade (engine) scripts from version 5.11 to 5.12 & 5.12 to 5.13…eg: activiti.h2.upgradestep.511.to.512.engine & activiti.h2.upgradestep.512.to.513.engine are not to be found… is this an expected omission? If so, what is the work-around (other than the one mentioned by tiesebarrell) since I assume that whenever the activiti-explorer .war starts up (I am using Tomcat 7.0.42), it tries to upgrade the schema (when necessary, i.e., in case the schema version is older or lesser than the version of activiti-explorer)… I am using h2 database (ver 1.3.173)…

Can you please help!

Regards,
A M Bharath, new Activiti developer

[trademak]

Please don't post the same question multiple times, see my answer in your other post.

[ambharath]

Thanks for the reply - will look at your reply in my other post and make sure not to duplicate questions.

-
A M Bharath