topic please consider the manual upgrade usecase in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/please-consider-the-manual-upgrade-usecase/m-p/93400#M63913 <HTML><HEAD></HEAD><BODY><SPAN>Hi,</SPAN><BR /><BR /><SPAN>I am currently investigating how we can best upgrade an existing live application from Activiti 5.8 to 5.9. Our deployments all have &lt;property name="databaseSchemaUpdate" value="false"/&gt; set because we need to control this process manually. The reason for this is that our application database do not have the rights to execute DDL, not uncommon from a security POV.</SPAN><BR /><BR /><SPAN>So i located the upgrade script org\activiti\db\upgrade\activiti.oracle.upgradestep.58.to.59.engine.sql and executed it on the target schema connected as an admin user. This worked fine, no errors. However restarting the application with Activiti 5.9 then gives me this error:</SPAN><BR /><BR /><PRE class="language-none line-numbers"><CODE><BR />Caused by: org.activiti.engine.ActivitiWrongDbException: version mismatch: activiti library version is '5.9', db version is 5.8 Hint: Set &lt;property name="databaseSchemaUpdate" to value="true" or value="create-drop" (use create-drop for testing only!) in bean processEngineConfiguration in activiti.cfg.xml for automatic schema creation<BR />&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.db.DbSqlSession.dbSchemaCheckVersion(DbSqlSession.java:492)<BR />&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.db.DbSqlSession.performSchemaOperationsProcessEngineBuild(DbSqlSession.java:884)<BR />&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.SchemaOperationsProcessEngineBuild.execute<BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE><BR /><SPAN>This means that there is still something being done in code to upgrade the DB, outside of the upgrade script ? Can we not make the upgrade script self-containing so that upgrades can be more easily managed by infra ? </SPAN><BR /><BR /><SPAN>For now i did this and it seems to be ok.</SPAN><BR /><BR /><PRE class="language-none line-numbers"><CODE><BR />UPDATE act_ge_property SET value_ = '5.9' WHERE name_='schema.version';<BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE><BR /><SPAN>I looked at the difference between an automatic upgrade, there the schema.history field is set as well but i don't think that information is actually used anywhere else.</SPAN><BR /><BR /><SPAN>Can anyone confirm this is a valid approach ?</SPAN></BODY></HTML> Tue, 06 Mar 2012 13:32:58 GMT heymjo 2012-03-06T13:32:58Z please consider the manual upgrade usecase https://connect.hyland.com/t5/alfresco-archive/please-consider-the-manual-upgrade-usecase/m-p/93400#M63913 Hi,I am currently investigating how we can best upgrade an existing live application from Activiti 5.8 to 5.9. Our deployments all have &lt;property name="databaseSchemaUpdate" value="false"/&gt; set because we need to control this process manually. The reason for this is that our application databa Tue, 06 Mar 2012 13:32:58 GMT https://connect.hyland.com/t5/alfresco-archive/please-consider-the-manual-upgrade-usecase/m-p/93400#M63913 heymjo 2012-03-06T13:32:58Z Re: please consider the manual upgrade usecase https://connect.hyland.com/t5/alfresco-archive/please-consider-the-manual-upgrade-usecase/m-p/93401#M63914 <HTML><HEAD></HEAD><BODY><SPAN>Same issue with 5.10.</SPAN><BR /><BR /><BR /><A href="http://jira.codehaus.org/browse/ACT-1343" rel="nofollow noopener noreferrer">http://jira.codehaus.org/browse/ACT-1343</A></BODY></HTML> Mon, 20 Aug 2012 15:35:53 GMT https://connect.hyland.com/t5/alfresco-archive/please-consider-the-manual-upgrade-usecase/m-p/93401#M63914 vlagorce 2012-08-20T15:35:53Z