Invalid Column Name after Updating from 7.9 to 7.10

Camunda 7 Topics Discussion & Questions
1

Hi,

Today i updated Camunda from Version 7.9 to 7.10. When i want to deploy a new simple Process i get following error.

ne.context|080-exec-6|11:02:04|ERROR|  ENGINE-16004 Exception while closing command context: ENGINE-03083 Exception while executing Batch Database Operations with message '
### Error flushing statements.  Cause: org.apache.ibatis.executor.BatchExecutorException: org.camunda.bpm.engine.impl.persistence.entity.ResourceEntity.insertResource (batch index #2) failed. 1 prior sub executor(s) completed successfully, but will be rolled back. Cause: java.sql.BatchUpdateException: Ungültiger Spaltenname "TYPE_".
### Cause: org.apache.ibatis.executor.BatchExecutorException: org.camunda.bpm.engine.impl.persistence.entity.ResourceEntity.insertResource (batch index #2) failed. 1 prior sub executor(s) completed successfully, but will be rolled back. Cause: java.sql.BatchUpdateException: Ungültiger Spaltenname "TYPE_".
java.sql.BatchUpdateException: Ungültiger Spaltenname "TYPE_".
'. Flush summary: 
 [
  INSERT DeploymentEntity[30817]
  INSERT ResourceEntity[30818]
  INSERT ProcessDefinitionEntity[Camunda7_10_Test:1:30819]
] org.camunda.bpm.engine.ProcessEngineException: ENGINE-03083 Exception while executing Batch Database Operations with message '
### Error flushing statements.  Cause: org.apache.ibatis.executor.BatchExecutorException: org.camunda.bpm.engine.impl.persistence.entity.ResourceEntity.insertResource (batch index #2) failed. 1 prior sub executor(s) completed successfully, but will be rolled back. Cause: java.sql.BatchUpdateException: Ungültiger Spaltenname "TYPE_".
### Cause: org.apache.ibatis.executor.BatchExecutorException: org.camunda.bpm.engine.impl.persistence.entity.ResourceEntity.insertResource (batch index #2) failed. 1 prior sub executor(s) completed successfully, but will be rolled back. Cause: java.sql.BatchUpdateException: Ungültiger Spaltenname "TYPE_".
java.sql.BatchUpdateException: Ungültiger Spaltenname "TYPE_".
'. Flush summary: 
 [
  INSERT DeploymentEntity[30817]
  INSERT ResourceEntity[30818]
  INSERT ProcessDefinitionEntity[Camunda7_10_Test:1:30819]
]
	at org.camunda.bpm.engine.impl.db.EnginePersistenceLogger.flushDbOperationsException(EnginePersistenceLogger.java:692)
	at org.camunda.bpm.engine.impl.db.entitymanager.DbEntityManager.flushDbOperations(DbEntityManager.java:361)
	at org.camunda.bpm.engine.impl.db.entitymanager.DbEntityManager.flushDbOperationManager(DbEntityManager.java:324)
	at org.camunda.bpm.engine.impl.db.entitymanager.DbEntityManager.flush(DbEntityManager.java:296)
	at org.camunda.bpm.engine.impl.interceptor.CommandContext.flushSessions(CommandContext.java:207)
	at org.camunda.bpm.engine.impl.interceptor.CommandContext.close(CommandContext.java:136)
	at org.camunda.bpm.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:115)
	at org.camunda.bpm.engine.impl.interceptor.ProcessApplicationContextInterceptor.execute(ProcessApplicationContextInterceptor.java:69)
	at org.camunda.bpm.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:32)
	at org.camunda.bpm.engine.impl.RepositoryServiceImpl.deployWithResult(RepositoryServiceImpl.java:101)
	at org.camunda.bpm.engine.impl.repository.DeploymentBuilderImpl.deployWithResult(DeploymentBuilderImpl.java:269)
	at org.camunda.bpm.engine.impl.repository.DeploymentBuilderImpl.deploy(DeploymentBuilderImpl.java:265)

Do i need a DB update or do i have to change something in my code?

Regards
Martin

2

Hi,

yes you are right. If you update your Camunda version you also have to upgrade the database. The sql-files for the update always come along with a new version. You can check out the update guide here:

https://docs.camunda.org/manual/7.10/update/minor/79-to-710/

Regards
Michael

1 Like
3

Thank you, 7.9 was the first version we used.

Update solved the issue.

4