Upgrade from 6.2.3 to 6.2.4 broke login

[Alexires]

Hi All,

I've just upgraded from OpenKM 6.2.3 to 6.2.4. I've followed the migration instructions, and upon trying to login with the okmadmin user, I get the following error:

Code: Select all

The system has generated an error
OKM-022024(getEnabledExtensions): OKM-022024
could not load an entity: [com.openkm.dao.bean.Profile#1]

The following is given in the catalina.log:

Code: Select all

2013-06-23 17:06:52,506 [http-apr-0.0.0.0-8080-exec-4] INFO  org.dozer.config.GlobalSettings - Trying to find Dozer configuration file: dozer.properties
2013-06-23 17:06:52,515 [http-apr-0.0.0.0-8080-exec-4] WARN  org.dozer.config.GlobalSettings - Dozer configuration file not found: dozer.properties.  Using defaults fo$
2013-06-23 17:06:52,519 [http-apr-0.0.0.0-8080-exec-4] INFO  org.dozer.DozerInitializer - Initializing Dozer. Version: 5.3.2, Thread Name: http-apr-0.0.0.0-8080-exec-4
2013-06-23 17:06:52,522 [http-apr-0.0.0.0-8080-exec-4] INFO  org.dozer.jmx.JMXPlatformImpl - Dozer JMX MBean [org.dozer.jmx:type=DozerStatisticsController] auto regist$
2013-06-23 17:06:52,524 [http-apr-0.0.0.0-8080-exec-4] INFO  org.dozer.jmx.JMXPlatformImpl - Dozer JMX MBean [org.dozer.jmx:type=DozerAdminController] auto registered $
2013-06-23 17:06:52,530 [http-apr-0.0.0.0-8080-exec-4] INFO  org.dozer.DozerBeanMapper - Initializing a new instance of dozer bean mapper.
2013-06-23 17:06:52,542 [http-apr-0.0.0.0-8080-exec-4] INFO  org.dozer.loader.CustomMappingsLoader - Using the following xml files to load custom mappings for the bean$
2013-06-23 17:06:52,543 [http-apr-0.0.0.0-8080-exec-4] INFO  org.dozer.loader.CustomMappingsLoader - Trying to find xml mapping file: dozerBeanMapping.xml
2013-06-23 17:06:52,544 [http-apr-0.0.0.0-8080-exec-4] INFO  org.dozer.loader.CustomMappingsLoader - Using URL [file:/home/alexires/tomcat/webapps/OpenKM/WEB-INF/class$
2013-06-23 17:06:52,556 [http-apr-0.0.0.0-8080-exec-4] INFO  org.dozer.loader.CustomMappingsLoader - Successfully loaded custom xml mappings from URL: [file:/home/alex$
2013-06-23 17:06:52,824 [http-apr-0.0.0.0-8080-exec-9] WARN  org.hibernate.util.JDBCExceptionReporter - SQL Error: 1054, SQLState: 42S22
2013-06-23 17:06:52,825 [http-apr-0.0.0.0-8080-exec-9] ERROR org.hibernate.util.JDBCExceptionReporter - Unknown column 'profile0_.PRF_TB_OMR_VIS' in 'field list'
2013-06-23 17:06:52,826 [http-apr-0.0.0.0-8080-exec-9] INFO  org.hibernate.event.def.DefaultLoadEventListener - Error performing load command
org.hibernate.exception.SQLGrammarException: could not load an entity: [com.openkm.dao.bean.Profile#1]
        at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:92)
        at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
        at org.hibernate.loader.Loader.loadEntity(Loader.java:2041)
        at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:86)
        at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:76)
        at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:3294)
        at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:496)
        at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:477)
        at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:227)
        at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:285)
        at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:152)
        at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:1090)

Any ideas what has gone wrong? I deleted the

Code: Select all

$TOMCAT_HOME/webapps/OpenKM

folder and the

Code: Select all

$TOMCAT_HOME/work/Catalina/localhost

folder as well.

[jllort]

have you changed OpenKM hibernate.hbmdll=update ? because what's sure is that OKM_PROFILE TABLE has not been updated correctly, and normally is caused because at startup hibernate has not update table structure.

[Alexires]

Yes, I did do that, and I just ran it again for good luck. Working now, for some reason...

Thanks anyway.