cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade from 1.3 to 1.4 fails

pknag
Champ in-the-making
Champ in-the-making
We are trying to upgrade our production system from 1.3 to 2.0 and as I understand that upgrading to 1.4 is necessary first step. I using the following steps:
a. do a full export from 1.3
b. run acp-upgrade scripts on the imports.
    This seems to change only one line in the xml file (the value for the version number)
c. setup a full import in 1.4
    I had to manually edit the xml files in acp files to remove duplicate childnames and then edit file names with characters that match a
    regular expression

When the actual import completes, the app fails to apply the database upgrade scripts. I do not understand why upgrade scripts are needed when I am doing a full import. The trace from alfresco log files are included.

Could anyone help me with this please?

PK

13:45:12,400 INFO  [org.alfresco.repo.admin.patch.PatchExecuter] Checking for patches to apply …13:45:12,449 ERROR [org.alfresco.repo.admin.patch.PatchServiceImpl] The schema upgrade script, 'classpath:alfresco/dbscripts/upgrade/1.4/${db.script.dialect}/AlfrescoSchemaUpdate-1.4-1.sql', has not been run against this database.13:45:12,734 ERROR [org.alfresco.repo.admin.patch.PatchExecuter] === Failed to apply patch         === ID: patch.schemaUpdateScript-V1.4-1RESULT: The schema upgrade script, 'classpath:alfresco/dbscripts/upgrade/1.4/${db.script.dialect}/AlfrescoSchemaUpdate-1.4-1.sql', has not been run against this database.=====================================13:45:12,816 ERROR [org.springframework.web.context.ContextLoader] Context initialization failedorg.alfresco.error.AlfrescoRuntimeException: Not all patches could be applied   at org.alfresco.repo.admin.patch.PatchExecuter.applyOutstandingPatches(PatchExecuter.java:98)   at org.alfresco.repo.admin.patch.PatchExecuter.onBootstrap(PatchExecuter.java:106)   at org.alfresco.util.AbstractLifecycleBean.onApplicationEvent(AbstractLifecycleBean.java:54)   at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:45)   at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:225)   at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:323)   at org.springframework.web.context.support.AbstractRefreshableWebApplicationContext.refresh(AbstractRefreshableWebApplicationContext.java:134)   at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:246)   at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:184)   at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:49)   at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3692)   at org.apache.catalina.core.StandardContext.start(StandardContext.java:4127)   at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)   at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:804)   at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:693)   at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:472)   at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1118)   at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)   at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1020)   at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012)   at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)   at org.apache.catalina.core.StandardService.start(StandardService.java:450)   at org.apache.catalina.core.StandardServer.start(StandardServer.java:680)   at org.apache.catalina.startup.Catalina.start(Catalina.java:536)   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)   at java.lang.reflect.Method.invoke(Method.java:597)   at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275)‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍
1 REPLY 1

pknag
Champ in-the-making
Champ in-the-making
Running the sql script manually results in error in line 33 of the file: AlfrescoSchemaUpdate-1.4-1.sql

I presume this table is not there because we never upgraded to 1.3, we started out with it. Should the table been there?

-PK

–– Upgrades to 1.3 of MyIsam tables could have missed the applied_patch table InnoDB–ALTER TABLE applied_patch        ENGINE = InnoDB;‍‍‍‍‍‍