I tried to move the Camunda tables in to a separate (Oracle) schema. Using a separate Spring datasource works fine, but I want to preserve transaction behaviour, so I tried the
databaseTablePrefix property (cf. https://docs.camunda.org/manual/7.6/reference/deployment-descriptors/tags/process-engine/).
Using this property, Camunda does not start up anymore, because there is table check, which obviously does not use the
databaseTablePrefix and fails. I found an old issue, which exactly describes this behaviour: https://app.camunda.com/jira/browse/CAM-3626, but is is closed and fixed since 7.3. We are currently running on 7.6.
Anyone has other ideas what else I can do to move Camunda tables to a separate schema?
@thorben, do you remember the bug issue I mentioned?