AnsweredAssumed Answered

Upgrade from 5.18.0 to 5.20.0

Question asked by sah209 on Jul 14, 2016
Latest reply on Jul 21, 2016 by sah209
This is a similar issue to following topic:
https://forums.activiti.org/content/database-upgrade-script-513-doesnt-alter-schemaversion-table

I started with v5.18.0 and wanted to upgrade to v5.20.0.

I executed following scripts from activiti-5.20.0/database/upgrade:
activiti.postgres.upgradestep.51800.to.51801.engine.sql
activiti.postgres.upgradestep.51801.to.52000.engine.sql
activiti.postgres.upgradestep.52000.to.52001.engine.sql
activiti.postgres.upgradestep.52001.to.52002.engine.sql


I wanted to see if there was any difference if I performed upgrade from 5.18.0 to 5.20.0 vs. using create scripts from 5.20.0 (activiti-5.20.0/database/create/activiti.postgres.create.engine.sql, activiti.postgres.create.history.sql, activiti.postgres.create.identity.sql)

The only difference that I can see in the pg_dump is data related (full export of schema and data)  is the following:

$ diff pg_dump_create-5.20.0.sql  pg_dump_upgrade-5.18.0_to_5.20.0.sql
< schema.version        5.20.0.2        1
< schema.history        create(5.20.0.2)        1

> schema.version        5.20.0.2        1
> schema.history        create(5.18.0.0)        1


Should I manually execute the following SQL, similar to what is seen in the other post I had found?

select VALUE_ from ACT_GE_PROPERTY where NAME_ = 'schema.history';
      value_     
——————
create(5.18.0.0)


update ACT_GE_PROPERTY set VALUE_ =
   (select VALUE_ || ' upgrade(5.18.0.0 -> 5.20.0.2)' from ACT_GE_PROPERTY where NAME_ = 'schema.history')
where NAME_ = 'schema.history';


select VALUE_ from ACT_GE_PROPERTY where NAME_ = 'schema.history';
                     value_                    
————————————————
create(5.18.0.0) upgrade(5.18.0.0 -> 5.20.0.2)


Thanks,
Scott

Outcomes