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:
- camunda-bpm-tomcat-7.13.0.zip\sql\upgrade\oracle_engine_7.10_patch_7.10.5_to_7.10.6.sql
- camunda-bpm-tomcat-7.13.0.zip\sql\upgrade\oracle_engine_7.10_patch_7.10.6_to_7.10.7.sql
- camunda-bpm-tomcat-7.13.0.zip\sql\upgrade\oracle_engine_7.10_patch_7.10.13_to_7.10.14.sql
- camunda-bpm-tomcat-7.13.0.zip\sql\upgrade\oracle_engine_7.10_to_7.11.sql
- camunda-bpm-tomcat-7.13.0.zip\sql\upgrade\oracle_engine_7.11_patch_7.11.2_to_7.11.3.sql
- camunda-bpm-tomcat-7.13.0.zip\sql\upgrade\oracle_engine_7.11_patch_7.11.7_to_7.11.8.sql
- camunda-bpm-tomcat-7.13.0.zip\sql\upgrade\oracle_engine_7.11_to_7.12.sql
- camunda-bpm-tomcat-7.13.0.zip\sql\upgrade\oracle_engine_7.12_patch_7.12.0_to_7.12.1.sql
- 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?