After updating from 2.5 to 3.4, I receive warnings/errors for some persisted items during bootup. My persistence DB is an external postgres DB hosted on a server on the web.
So far, this service works fine and I receive all persisted values when trying to work with them on charts or in rules.
But: during bootup I receive the following warning for 6 items:
2023-02-16 01:22:49.895 [WARN ] [jdbc.internal.JdbcPersistenceService] - JDBC::query: Unable to query item
org.openhab.persistence.jdbc.internal.exceptions.JdbcSQLException: Error in SQL query!!!; ERROR: relation "mobilejohanlastseen_0102" does not exist
Position: 25 Query: SELECT time, value FROM mobilejohanlastseen_0102 ORDER BY time DESC OFFSET 0 LIMIT 1 Parameters: []; Pool Name= yank-default; SQL= SELECT time, value FROM mobilejohanlastseen_0102 ORDER BY time DESC OFFSET 0 LIMIT 1
at org.openhab.persistence.jdbc.internal.db.JdbcBaseDAO.doGetHistItemFilterQuery(JdbcBaseDAO.java:469) ~[bundleFile:?]
at org.openhab.persistence.jdbc.internal.JdbcMapper.getHistItemFilterQuery(JdbcMapper.java:238) ~[bundleFile:?]
at org.openhab.persistence.jdbc.internal.JdbcPersistenceService.query(JdbcPersistenceService.java:226) [bundleFile:?]
at jdk.internal.reflect.GeneratedMethodAccessor124.invoke(Unknown Source) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
at org.openhab.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:154) [bundleFile:?]
at org.openhab.core.internal.common.Invocation.call(Invocation.java:52) [bundleFile:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:829) [?:?]
I already checked the DB if these tables exist or if the number of the item-table changed but everything is in place and is available.
JDBC is configured in jdbc.cfg with the following lines:
[...]
# url=jdbc:sqlite:./testSqlite.db
url=jdbc:postgresql://serverurl:port/dbname
# required database user
user=mysecretusername
# required database password
password=123456789
[...]
# Tablename Prefix generation, using Item real names or "item" (optional, default: false -> "item")
# If true, 'tableNamePrefix' is ignored.
tableUseRealItemNames=true
[...]
Maybe worth to be mentioned: My internet connection is 4G.