Startup failure and other Query woes on Db2 databases with Activiti 9+
Author: lmoroczCreated Jul 3, 2025Updated Apr 28, 2026
Sadly there are still multiple issues with Activiti 9+ and Db2 databases.
- Only UNIQUE indexes can use the
INCLUDEkeyword in Db2 resultingSQLCODE=-628startup error oncreate index ACT_IDX_IDENT_LNK_TASKDDL. I had to modify the corresponding create index DDL-s, to even start new Spring Boot 4.0.6 app with Db2 database and Activiti. - TaskQuery execution exception with rank filtering & ordering:
ReflectionException: There is no getter for property named 'v3_after_withLimit' in 'class org.activiti.engine.impl.TaskQueryImpl' - HistoricProcessInstanceQuery execution exception with rank filtering & ordering:
ReflectionException: There is no getter for property named 'v3_after_withLimit' in 'class org.activiti.engine.impl.HistoricProcessInstanceQueryImpl' - HistoricTaskInstanceQuery execution exception with rank filtering & ordering:
SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-104, SQLSTATE=42601, SQLERRMC=);ORDER BY rnk(This was already an issue with Activiti 8.x, but I updated this issue with the new woes from Activiti 9+)
See activiti-db2-#5068.zip for the reproducer app. Remove the fixed files from src\main\resources\org\activiti\db\* then run the DemoApplicationTests JUnit test. (The Db2 container needs some time, usually 1+ minute, to startup properly).
Activiti version: 9.0.0 (also with 9.1.0-alpha.16)
DB2 version: (latest) icr.io/db2_community/db2 (v12.1.0) image on podman (also with 11.5.x Db2 versions)
Source: Activiti/Activiti