What's the recommended way of running the SQL update scripts?

Camunda 7 Topics Discussion & Questions
1

Hi guys,

We have Camunda 7.10 community edition in PROD and we would like to upgrade to 7.13 also community edition and am a bit confused as to the proper order to run the SQL update scripts that are packaged inside your distribution archive at:
https://downloads.camunda.cloud/release/camunda-bpm/tomcat/7.13/camunda-bpm-tomcat-7.13.0.zip

There seems to be SQL scripts that upgrade:

  1. camunda-bpm-tomcat-7.13.0.zip\sql\upgrade\oracle_engine_7.10_patch_7.10.5_to_7.10.6.sql
  2. camunda-bpm-tomcat-7.13.0.zip\sql\upgrade\oracle_engine_7.10_patch_7.10.6_to_7.10.7.sql
  3. camunda-bpm-tomcat-7.13.0.zip\sql\upgrade\oracle_engine_7.10_patch_7.10.13_to_7.10.14.sql
  4. camunda-bpm-tomcat-7.13.0.zip\sql\upgrade\oracle_engine_7.10_to_7.11.sql
  5. camunda-bpm-tomcat-7.13.0.zip\sql\upgrade\oracle_engine_7.11_patch_7.11.2_to_7.11.3.sql
  6. camunda-bpm-tomcat-7.13.0.zip\sql\upgrade\oracle_engine_7.11_patch_7.11.7_to_7.11.8.sql
  7. camunda-bpm-tomcat-7.13.0.zip\sql\upgrade\oracle_engine_7.11_to_7.12.sql
  8. camunda-bpm-tomcat-7.13.0.zip\sql\upgrade\oracle_engine_7.12_patch_7.12.0_to_7.12.1.sql
  9. camunda-bpm-tomcat-7.13.0.zip\sql\upgrade\oracle_engine_7.12_to_7.13.sql

However, we noticed that the ACT_IDX_HI_ACT_INST_START_END index is being created three times. First in oracle_engine_7.10_patch_7.10.13_to_7.10.14.sql, a second time in oracle_engine_7.11_patch_7.11.7_to_7.11.8.sql and a third time in oracle_engine_7.12_patch_7.12.0_to_7.12.1.sql causing the second script to fail creating the index since it already exists.

Does that mean we do not need to run the bug fix upgrade scripts? And only run the minor upgrade scripts? (or is this a bug in the SQL update scripts?).

Also, does Camunda support rollback? Or must we create our rollback scripts?

1 Like
2

Hi @Louislu,

you can read more about databse patches here: https://docs.camunda.org/manual/7.13/update/patch-level/#database-patches

In the docs you can see that the two scripts adress the same issue. Release 7.11.8 overlaps with 712.1 and you only need to run one of the scripts.

Camunda didn’t offer scripts to rollback your database. The engine is able to run with a database version upgraded with one version: https://docs.camunda.org/manual/7.13/update/rolling-update/

To be safe, make a backup of your database.

Hope this helps, Ingo

3