topic Re: 5.10->5.12 db schema migration problem in Alfresco Archive

5.10->5.12 db schema migration problem

pgadecki — Tue, 19 Mar 2013 15:36:51 GMT

It seems that there is a problem when trying to start activiti-engine:5.12 on Oracle database with activiti:5.10 tables and schema update policy set to: ProcessEngineConfigurationImpl.DB_SCHEMA_UPDATE_DROP_CREATEI think that it might try to perform drop for 5.12 and it fails, then while creating tab

Re: 5.10->5.12 db schema migration problem

groopk — Tue, 19 Mar 2013 19:51:34 GMT

Not to hijack your thread, but to add on to it, we get the following going from 5.11 to 5.12:


org.apache.ibatis.exceptions.PersistenceException:
### Error updating database.  Cause: org.h2.jdbc.JdbcSQLException: Referential integrity constraint violation: "ACT_FK_I
DL_PROCINST: PUBLIC.ACT_RU_IDENTITYLINK FOREIGN KEY(PROC_INST_ID_) REFERENCES PUBLIC.ACT_RU_EXECUTION(ID_) ('2713')"; SQ
L statement:
delete from ACT_RU_EXECUTION where ID_ = ? and REV_ = ? [23503-169]
        at org.h2.message.DbException.getJdbcSQLException(DbException.java:329)
        ….
### The error may involve org.activiti.engine.impl.persistence.entity.ExecutionEntity.deleteExecution-Inline
### The error occurred while setting parameters
### SQL: delete from ACT_RU_EXECUTION where ID_ = ? and REV_ = ?
### Cause: org.h2.jdbc.JdbcSQLException: Referential integrity constraint violation: "ACT_FK_IDL_PROCINST: PUBLIC.ACT_RU
_IDENTITYLINK FOREIGN KEY(PROC_INST_ID_) REFERENCES PUBLIC.ACT_RU_EXECUTION(ID_) ('2713')"; SQL statement:
delete from ACT_RU_EXECUTION where ID_ = ? and REV_ = ? [23503-169]
        at org.h2.message.DbException.getJdbcSQLException(DbException.java:329)
        ….
Caused by: org.h2.jdbc.JdbcSQLException: Referential integrity constraint violation: "ACT_FK_IDL_PROCINST: PUBLIC.ACT_RU
_IDENTITYLINK FOREIGN KEY(PROC_INST_ID_) REFERENCES PUBLIC.ACT_RU_EXECUTION(ID_) ('2713')"; SQL statement:
delete from ACT_RU_EXECUTION where ID_ = ? and REV_ = ? [23503-169]
        at org.h2.message.DbException.getJdbcSQLException(DbException.java:329)
        ….
Exception in thread "Thread-3" org.apache.ibatis.exceptions.PersistenceException:
### Error updating database.  Cause: org.h2.jdbc.JdbcSQLException: Referential integrity constraint violation: "ACT_FK_I
DL_PROCINST: PUBLIC.ACT_RU_IDENTITYLINK FOREIGN KEY(PROC_INST_ID_) REFERENCES PUBLIC.ACT_RU_EXECUTION(ID_) ('2713')"; SQ
L statement:
delete from ACT_RU_EXECUTION where ID_ = ? and REV_ = ? [23503-169]
        at org.h2.message.DbException.getJdbcSQLException(DbException.java:329)
        ….
### The error may involve org.activiti.engine.impl.persistence.entity.ExecutionEntity.deleteExecution-Inline
### The error occurred while setting parameters
### SQL: delete from ACT_RU_EXECUTION where ID_ = ? and REV_ = ?
### Cause: org.h2.jdbc.JdbcSQLException: Referential integrity constraint violation: "ACT_FK_IDL_PROCINST: PUBLIC.ACT_RU
_IDENTITYLINK FOREIGN KEY(PROC_INST_ID_) REFERENCES PUBLIC.ACT_RU_EXECUTION(ID_) ('2713')"; SQL statement:
delete from ACT_RU_EXECUTION where ID_ = ? and REV_ = ? [23503-169]
        at org.h2.message.DbException.getJdbcSQLException(DbException.java:329)
        …
Caused by: org.h2.jdbc.JdbcSQLException: Referential integrity constraint violation: "ACT_FK_IDL_PROCINST: PUBLIC.ACT_RU
_IDENTITYLINK FOREIGN KEY(PROC_INST_ID_) REFERENCES PUBLIC.ACT_RU_EXECUTION(ID_) ('2713')"; SQL statement:
delete from ACT_RU_EXECUTION where ID_ = ? and REV_ = ? [23503-169]
        at org.h2.message.DbException.getJdbcSQLException(DbException.java:329)

Not too big of a deal for us, we can just wipe the DB and start over, we are still in development mode. but FYI.

Re: 5.10->5.12 db schema migration problem

pgadecki — Wed, 20 Mar 2013 08:45:46 GMT

Not too big of a deal for us, we can just wipe the DB and start over, we are still in development mode. but FYI.

Yeah, same story here, but it's still a problem.

Re: 5.10->5.12 db schema migration problem

jbarrez — Wed, 20 Mar 2013 10:12:05 GMT

@pgadecki: so am I understanding you correctly: the create should never have started if the drop didn't succeed? And that is exactly what DOES happen now?

@ groopk: when do you see this error? Do you have a simple test case that can demonstrate the problem?

Re: 5.10->5.12 db schema migration problem

pgadecki — Wed, 20 Mar 2013 14:34:48 GMT

@pgadecki: so am I understanding you correctly: the create should never have started if the drop didn't succeed? And that is exactly what DOES happen now?

What is important is the reason why drop didn't succeed (I'm guessing that it's beceause it was executing a drop sql for 5.12 not for 5.10 on 5.10 schema, correct me if I'm wrong). As long as ACT_GE_PROPERTY keeps current activiti db schema.version this value could be used to select proper drop sql file version.

Re: 5.10->5.12 db schema migration problem

jbarrez — Thu, 21 Mar 2013 11:19:50 GMT

That's a valid point. However, most database don't offer transactions for DDL (which would simplify things ENORMOUSLY), and you can't be sure what has been dropped/created. So resetteing the version would also be kinda wrong, as you are probably somewhere 'in between' versions.