Error after migration from 5.0.4 to 5.1.8

[Peter81929]

Hi all,

after following the migration guide instructions, I am unable to start 5.1.8 after migration form 5.0.4 and I could not find the error.

Error log:

Code: Select all

23:11:06,888 INFO  [DefaultWebAppDesciptorModifierImpl] Ignore servlet: com.openkm.servlet.admin.DataBrowserServlet
23:11:06,889 INFO  [DefaultWebAppDesciptorModifierImpl] Ignore servlet: com.openkm.servlet.TestServlet
23:11:06,953 INFO  [TomcatDeployer] deploy, ctxPath=/OpenKM, warUrl=.../tmp/deploy/tmp6331444727291206708OpenKM-exp.war/
23:11:11,977 WARN  [JDBCExceptionReporter] SQL Error: -22, SQLState: S0002
23:11:11,977 ERROR [JDBCExceptionReporter] Table not found in statement [/* from Config cfg where cfg.key=:key */ select top ? config0_.CFG_KEY as CFG1_32_, config0_.CFG_TYPE as CFG2_32_, config0_.CFG_VALUE as CFG3_32_ from OKM_CONFIG config0_ where config0_.CFG_KEY=?]
23:11:11,979 ERROR [Config] ** Error reading configuration table **
23:11:11,983 ERROR [[/OpenKM]] StandardWrapper.Throwable
java.lang.NullPointerException
	at java.io.File.<init>(File.java:222)
	at com.openkm.servlet.RepositoryStartupServlet.init(RepositoryStartupServlet.java:98)
	at javax.servlet.GenericServlet.init(GenericServlet.java:212)
	at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)

Any ideas?

Thanks, Peter

[chevdor]

I had issue following the official 5.0.4 to 5.1.8 migration steps.

Here is what I did:
- unzip 5.1.8
- leave default settings
- start openKM
- once started, change create to none in the config file
- restart
- create your users (I have only one... I re-created it manually as the scripts from the 5.0.4 backup did not work)
- stop openKM
- copy your repository file and folder into the new openKM installation
- restart openKM

With this process, *almost* everything works fine. The only issues I have are:
- I lost my keywords (If someone can give me a hint how to export -> reimport them, I take it !)
- I lost my searches

[Peter81929]

Thanks for the checklist, works for me as well.

Not the best practice solution but a work around.

I would very much appreciate an update/upgrade feature within(!) OpenKM. It's annoying to get through that flaky process again and again.

Best regards, Peter

[jllort]

From version 6.0 will be more easier upgrading because we'll take total control of database. Now someone is in jackrabbit hand and that has caused some limitations. We think the last difficult migration procedure will be between 5.1.X to 6.0 after it we think all will be more easilly.