My team is trying to upgrade from 6.1.0.0 to 6.3.1.0 using the provided mssql scripts to run on our own database. When we try to run the engine after applying the update, we’re getting the error Invalid column name 'CALLBACK_ID_'.
for table ACT_HI_PROCINST
. Looking through the provided scripts, it seems the create scripts for ACT_HI_PROCINST in 6.2 and 6.3 each include that column, but it’s not added anywhere in the upgrade scripts from 6.1 to 6.3. Was this missed somehow? Or am I misunderstanding something about the scripts or file structure?
The changes should be here: https://github.com/flowable/flowable-engine/blob/master/modules/flowable-engine/src/main/resources/org/flowable/db/upgrade/flowable.mssql.upgradestep.6120.to.6200.history.sql (upgrade from 6.1.2 to 6.2.0). So as far as I can see, they are applied. Are you using the auto-upgrade of the engine?
Can you paste the logging that you see when booting up? It should tell which updates are applied.
We are not using auto-upgrade. When I download Flowable 6.3.1 from https://www.flowable.org/, unzip, and open flowable-6.3.1/database/upgrade/bpmn/flowable.mssql.upgradestep.6120.to.6200.history.sql
, this is what’s in the file:
alter table ACT_HI_TASKINST add SCOPE_ID_ nvarchar(255);
alter table ACT_HI_TASKINST add SUB_SCOPE_ID_ nvarchar(255);
alter table ACT_HI_TASKINST add SCOPE_TYPE_ nvarchar(255);
alter table ACT_HI_TASKINST add SCOPE_DEFINITION_ID_ nvarchar(255);
create index ACT_IDX_HI_TASK_SCOPE on ACT_HI_TASKINST(SCOPE_ID_, SCOPE_TYPE_);
create index ACT_IDX_HI_TASK_SUB_SCOPE on ACT_HI_TASKINST(SUB_SCOPE_ID_, SCOPE_TYPE_);
create index ACT_IDX_HI_TASK_SCOPE_DEF on ACT_HI_TASKINST(SCOPE_DEFINITION_ID_, SCOPE_TYPE_);
alter table ACT_HI_VARINST add SCOPE_ID_ nvarchar(255);
alter table ACT_HI_VARINST add SUB_SCOPE_ID_ nvarchar(255);
alter table ACT_HI_VARINST add SCOPE_TYPE_ nvarchar(255);
create index ACT_IDX_HI_VAR_SCOPE_ID_TYPE on ACT_HI_VARINST(SCOPE_ID_, SCOPE_TYPE_);
create index ACT_IDX_HI_VAR_SUB_ID_TYPE on ACT_HI_VARINST(SUB_SCOPE_ID_, SCOPE_TYPE_);
ACT_HI_PROCINST is not altered. So when we used the update
scripts to update our MSSQL database, we got SQL errors. We looked at the create
script and saw it had those two lines, so we added those, and so far it is running smoothly. It seems like there may be a problem with how the upgrade
script was generated, and I’m not sure if it affected only mssql or others as well.