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

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

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>