Why camunda cannot create tables in two schema of same db?


The db have two schema. The first call “A”, the second called “B”.

At the first my database config connected the "A’ schema.
When I run my application the camunda created the tables in the “A” schema.

After that I changed my database config connect to “B” schema and run the application again but the camunda was not created the tables in the schema “B” and throwed an exception.
The exception says camunda cannot find the table “ATU_xxx”.

This make me confused and then I read the source code find the camunda will check the whole db to check tables is or not created.

In my case the tables in the “A” schema, the camunda think the tables are exists. Then camunda will to connection to the schema “B” to find the table. The tables does not exists in the “B” so camunda throwed that error.

This is a bug or not ? How to fix it ?

My english does not good, please forgive me.


Hi @himly,

Can you provide any more information about your db and engine setup? Did you completely remove the connection to the “A” schema form the Process Engine configuration file?

What is the version of the Camunda engine you are using?

The Camunda engine will create all the necessary tables when an empty db schema is provided.