Flowable upgrade to 7.0.1 version issues

1

Hi Team,

i am trying to upgrade to latest Flowable Version 7.0.1. I am running upgrade through microservices by adding the latest version dependency in pom.xml

Everytime i am getting an error that index already exists,

create index ACT_IDX_EJOB_SCOPE_DEF on ACT_RU_EXTERNAL_JOB(SCOPE_DEFINITION_ID_, SCOPE_TYPE_)

create index ACT_IDX_HI_PRO_SUPER_PROCINST on ACT_HI_PROCINST(SUPER_PROCESS_INSTANCE_ID_)ORA: 01408: such column list already indexed’

statement create index ACT_IDX_EJOB_SUB_SCOPE on ACT_RU_EXTERNAL_JOB(SUB_SCOPE_ID_, SCOPE_TYPE_)

15:48:07.452: [APP/PROC/WEB.0] java.sql.SQLSyntaxErrorException: ORA-00955: name is already used by an existing object

WHat could be the reason, and is there an easy way to upgrade flowable directly on DB side and not initiating from microservice. a one script

2

Hey @MrAb,

From which version are you upgrading? This particular index was added in 6.5.1.

Yes there is. If you download the zip from our release e.g. Release Flowable 7.0.1 release · flowable/flowable-engine · GitHub you’ll see that in database → upgrade → all you will find the scripts from updating from one version to another. You can run the scripts manually if you want to.

Cheers,
Filip

3

I am upgrading from 6.5.0.6

but during the upgrade steps via application, it throws the error index exists and force stops the application start up.

4

Screenshot 2024-08-19 at 3.16.29 AM
Screenshot 2024-08-19 at 3.16.29 AM998×1228 216 KB

Just these scripts are enough or should i run flowable.cockroach, flowable.db2, flowable.h2, flowable.hsql, flowable.mssql, flowable.mssql55, flowable.oracle, flowable.postgres,

5

and i see such scripts in different packages like

flowable-engine,
flowable-engine-common
flowable-engine-common-api

and so on

should i just run all the scripts present in flowable-engine-* pacakge

6

I disabled all the engines

flowable:
dmn:
enabled: false
cmmn:
enabled: false
form:
enabled: false
content:
enabled: false
app:
enabled: false
eventregistry:
enabled: false

i am using only bpmn

7

These are the steps in order, i had to make it work

I am upgrading from 6.5.0.6 to 7.0.1 with java17 and spring boot 3.2.x
with this engines disabled

flowable:
dmn:
enabled: false
cmmn:
enabled: false
form:
enabled: false
content:
enabled: false
app:
enabled: false
eventregistry:
enabled: false

First error is from JobDBSchemaManager:

performing upgrade on job with resource org/flowable/job/service/db/upgrade/flowable.oracle.upgradestep.6512.to.6513.job.sql

problem during schema upgrade, statement create table ACT_RU_EXTERNAL_JOB (
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT ID_ NVARCHAR2(64) NOT NULL,
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT REV_ INTEGER,
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT CATEGORY_ NVARCHAR2(255),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT TYPE_ NVARCHAR2(255) NOT NULL,
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT LOCK_EXP_TIME_ TIMESTAMP(6),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT LOCK_OWNER_ NVARCHAR2(255),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT EXCLUSIVE_ NUMBER(1,0) CHECK (EXCLUSIVE_ IN (1,0)),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT EXECUTION_ID_ NVARCHAR2(64),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT PROCESS_INSTANCE_ID_ NVARCHAR2(64),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT PROC_DEF_ID_ NVARCHAR2(64),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT ELEMENT_ID_ NVARCHAR2(255),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT ELEMENT_NAME_ NVARCHAR2(255),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT SCOPE_ID_ NVARCHAR2(255),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT SUB_SCOPE_ID_ NVARCHAR2(255),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT SCOPE_TYPE_ NVARCHAR2(255),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT SCOPE_DEFINITION_ID_ NVARCHAR2(255),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT RETRIES_ INTEGER,
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT EXCEPTION_STACK_ID_ NVARCHAR2(64),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT EXCEPTION_MSG_ NVARCHAR2(2000),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT DUEDATE_ TIMESTAMP(6),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT REPEAT_ NVARCHAR2(255),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT HANDLER_TYPE_ NVARCHAR2(255),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT HANDLER_CFG_ NVARCHAR2(2000),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT CUSTOM_VALUES_ID_ NVARCHAR2(64),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT CREATE_TIME_ TIMESTAMP(6),
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT TENANT_ID_ NVARCHAR2(255) DEFAULT ‘’,
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT primary key (ID_)
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT )
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT java.sql.SQLSyntaxErrorException: ORA-00955: name is already used by an existing object

at
2024-08-16T14:56:09.35-0400 [APP/PROC/WEB/0] OUT at org.flowable.common.engine.impl.db.AbstractSqlScriptBasedDbSchemaManager.executeSchemaResource(AbstractSqlScriptBasedDbSchemaManager.java:325) ~[flowable-engine-common-7.0.1.jar:7.0.1]

at

problem during schema upgrade, statement create index ACT_IDX_EJOB_CUSTOM_VAL_ID on ACT_RU_EXTERNAL_JOB(CUSTOM_VALUES_ID_)

problem during schema upgrade, statement create index ACT_IDX_EJOB_SUB_SCOPE on ACT_RU_EXTERNAL_JOB(SUB_SCOPE_ID_, SCOPE_TYPE_)

problem during schema upgrade, statement create index ACT_IDX_EJOB_SCOPE_DEF on ACT_RU_EXTERNAL_JOB(SCOPE_DEFINITION_ID_, SCOPE_TYPE_)

2024-08-16T14:56:09.53-0400 [APP/PROC/WEB/0] OUT java.sql.SQLSyntaxErrorException: ORA-00955: name is already used by an existing object

So i restarted the service, since it failed , now the error was at o.f.e.impl.db.ProcessDbSchemaManager

problem during schema upgrade, statement create index ACT_IDX_HI_PRO_SUPER_PROCINST on ACT_HI_PROCINST(SUPER_PROCESS_INSTANCE_ID_)
2024-08-16T17:32:04.48-0400 [APP/PROC/WEB/0] OUT java.sql.SQLException: ORA-01408: such column list already indexed

ouldn’t upgrade db schema: create index ACT_IDX_HI_PRO_SUPER_PROCINST on ACT_HI_PROCINST(SUPER_PROCESS_INSTANCE_ID_)

So i restarted again,
this time application started with no errors