I believe there is a bug in the automatic creation of the Camunda tables in the following use case:
Use Case: I have two different Springboot Applications that use Camunda. They both use the same Oracle Database Server, but they connect to different Schemas of this database server.
The application that gets deployed first (for the first time), is deployed successfully and all Camunda tables are created automatically.
However, the second application, will get the following error:
Caused by: org.apache.ibatis.exceptions.PersistenceException:
### Error querying database. Cause: java.sql.SQLSyntaxErrorException: Table 'atm.act_ge_property' doesn't exist
### The error may exist in org/camunda/bpm/engine/impl/mapping/entity/Property.xml
### The error may involve org.camunda.bpm.engine.impl.persistence.entity.PropertyEntity.selectProperty-Inline
### The error occurred while setting parameters
### SQL: select * from ACT_GE_PROPERTY where NAME_ = ?
### Cause: java.sql.SQLSyntaxErrorException: Table 'atm.act_ge_property' doesn't exist
I found a related issue (Exception when starting Spring Boot project - Table atm.act_ge_property doesn't exist)
but unfortunately the solution doesn’t seem to work for Oracle databases.
Is this a bug? Is there a workaround for this issue?
As a bonus question: Is there a way I can define the properties camunda.bpm.database.schema-name and table-prefix, and also add the schema-update = true property? If I add schema-name and table-prefix, then it always forces the creation of new tables.
Thanks in advance