historyLevel mismatch exception

[roleba...@gmail.com]

How to solve the following exception?
CHWERWIEGEND: ENGINE-16004 Exception while closing command context: historyLevel mismatch: configuration says HistoryLevelFull(name=full, id=3) and database says HistoryLevelAudit(name=audit, id=2)
org.camunda.bpm.engine.ProcessEngineException: historyLevel mismatch: configuration says HistoryLevelFull(name=full, id=3) and database says HistoryLevelAudit(name=audit, id=2)
at org.camunda.bpm.engine.impl.SchemaOperationsProcessEngineBuild.checkHistoryLevel(SchemaOperationsProcessEngineBuild.java:108)

There is only the value "full" in the reference https://docs.camunda.org/manual

[roleba...@gmail.com]

The exception above occurs during starting up of tomcat with a shared process engine while using an already filled shared database. The exception prevents tomcat from starting up.

[thorben....@camunda.com]

Hi,

Apparently the engine that initially filled the database used history level audit. An engine with history level full can't work with it because it expects certain history entries to exist. Thus, you should configure the current shared engine with history level audit as well (in bpm-platform.xml in Tomcat's conf folder have a look at the process-engine element). See the deployment descriptor reference [1] that lists the names of the available history levels.

Cheers,
Thorben

[1] https://docs.camunda.org/manual/latest/reference/deployment-descriptors/tags/process-engine/#configuration-properties

[roleba...@gmail.com]

I changed the value to "audit" and now everything works fine. Thank you!