Database issue while upgrading flowable from 6.5.2 to 6.7.2

1

Hi Team,

We are trying to upgrade flowable from 6.5.2 to 6.7.2, while upgrading we are database exceptions.
Sometime throwing major minor version mismatch error, sometime throwing act_ge_property table not found.

Even if I am trying to run fresh flowable with DB, which is having multiple schemas, its throwing act_ge_property table not found(Flowable is update DB script rather then create).

Regards,
Ashish Singh

2

Can you paste which exceptions?

That exception can only happen when using an old engine on a newer schema.

3

Hi,

Please see below for exception.

Caused by: java.sql.SQLSyntaxErrorException: Table ‘local.act_ge_property’ doesn’t exist
at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:120) ~[mysql-connector-java-8.0.28.jar:8.0.28]
at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122) ~[mysql-connector-java-8.0.28.jar:8.0.28]
at com.mysql.cj.jdbc.ClientPreparedStatement.executeInternal(ClientPreparedStatement.java:953) ~[mysql-connector-java-8.0.28.jar:8.0.28]
at com.mysql.cj.jdbc.ClientPreparedStatement.execute(ClientPreparedStatement.java:371) ~[mysql-connector-java-8.0.28.jar:8.0.28]
at com.zaxxer.hikari.pool.ProxyPreparedStatement.execute(ProxyPreparedStatement.java:44) ~[HikariCP-4.0.3.jar:na]
at com.zaxxer.hikari.pool.HikariProxyPreparedStatement.execute(HikariProxyPreparedStatement.java) ~[HikariCP-4.0.3.jar:na]
at org.apache.ibatis.executor.statement.PreparedStatementHandler.query(PreparedStatementHandler.java:63) ~[mybatis-3.4.6.jar:3.4.6]
at org.apache.ibatis.executor.statement.RoutingStatementHandler.query(RoutingStatementHandler.java:79) ~[mybatis-3.4.6.jar:3.4.6]
at org.apache.ibatis.executor.SimpleExecutor.doQuery(SimpleExecutor.java:63) ~[mybatis-3.4.6.jar:3.4.6]
at org.apache.ibatis.executor.BaseExecutor.queryFromDatabase(BaseExecutor.java:326) ~[mybatis-3.4.6.jar:3.4.6]
at org.apache.ibatis.executor.BaseExecutor.query(BaseExecutor.java:156) ~[mybatis-3.4.6.jar:3.4.6]
at org.apache.ibatis.executor.CachingExecutor.query(CachingExecutor.java:109) ~[mybatis-3.4.6.jar:3.4.6]
at org.apache.ibatis.executor.CachingExecutor.query(CachingExecutor.java:83) ~[mybatis-3.4.6.jar:3.4.6]
at org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:148) ~[mybatis-3.4.6.jar:3.4.6]
… 102 common frames omitted

4

We are just upgrading flowable engine from 6.5.2 to 6.7.2.
We are using Maria DB

5

Hi Team,

After debugging the flowable code I have found bug in flowable source code.
Normally if we have one Schema in Database Create/ Upgrade works but if we have multiple schemas(One flowable schemas and others for different use) in Database it fails to Create flowable Schemas.

It throws Table ‘local.act_ge_property’ doesn’t exist.

6

If you’re using multiple schema’s, the engine also needs to be configured to use that schema. But this has always been the case - also in 6.5.x - so not sure how it could work back then?