After upgrade to 1.4.97 from 1.4.96 produces the following exception : org.h2.jdbc.JdbcSQLException: Table "SYNONYMS" not found;

411 views
Skip to first unread message

Meni Hillel

unread,
Apr 13, 2018, 4:30:05 AM4/13/18
to H2 Database
org.h2.jdbc.JdbcSQLException: Table "SYNONYMS" not found; SQL statement:
SELECT TABLE_CAT, TABLE_SCHEM, TABLE_NAME, TABLE_TYPE, REMARKS, TYPE_CAT, TYPE_SCHEM, TYPE_NAME, SELF_REFERENCING_COL_NAME, REF_GENERATION, SQL FROM (SELECT SYNONYM_CATALOG TABLE_CAT, SYNONYM_SCHEMA TABLE_SCHEM, SYNONYM_NAME as TABLE_NAME, TYPE_NAME AS TABLE_TYPE, REMARKS, TYPE_NAME TYPE_CAT, TYPE_NAME TYPE_SCHEM, TYPE_NAME AS TYPE_NAME, TYPE_NAME SELF_REFERENCING_COL_NAME, TYPE_NAME REF_GENERATION, NULL AS SQL FROM INFORMATION_SCHEMA.SYNONYMS WHERE SYNONYM_CATALOG LIKE ? ESCAPE ? AND SYNONYM_SCHEMA LIKE ? ESCAPE ? AND SYNONYM_NAME LIKE ? ESCAPE ? AND (true)  UNION SELECT TABLE_CATALOG TABLE_CAT, TABLE_SCHEMA TABLE_SCHEM, TABLE_NAME, TABLE_TYPE, REMARKS, TYPE_NAME TYPE_CAT, TYPE_NAME TYPE_SCHEM, TYPE_NAME, TYPE_NAME SELF_REFERENCING_COL_NAME, TYPE_NAME REF_GENERATION, SQL FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_CATALOG LIKE ? ESCAPE ? AND TABLE_SCHEMA LIKE ? ESCAPE ? AND TABLE_NAME LIKE ? ESCAPE ? AND (TRUE) ) ORDER BY TABLE_TYPE, TABLE_SCHEM, TABLE_NAME [42102-196]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.schema.Schema.getTableOrView(Schema.java:456)
at org.h2.command.Parser.readTableOrView(Parser.java:5535)
at org.h2.command.Parser.readTableFilter(Parser.java:1266)
at org.h2.command.Parser.parseSelectSimpleFromPart(Parser.java:1946)
at org.h2.command.Parser.parseSelectSimple(Parser.java:2095)
at org.h2.command.Parser.parseSelectSub(Parser.java:1940)
at org.h2.command.Parser.parseSelectUnion(Parser.java:1755)
at org.h2.command.Parser.readTableFilter(Parser.java:1190)
at org.h2.command.Parser.parseSelectSimpleFromPart(Parser.java:1946)
at org.h2.command.Parser.parseSelectSimple(Parser.java:2095)
at org.h2.command.Parser.parseSelectSub(Parser.java:1940)
at org.h2.command.Parser.parseSelectUnion(Parser.java:1755)
at org.h2.command.Parser.parseSelect(Parser.java:1743)
at org.h2.command.Parser.parsePrepared(Parser.java:449)
at org.h2.command.Parser.parse(Parser.java:321)
at org.h2.command.Parser.parse(Parser.java:293)
at org.h2.command.Parser.prepareCommand(Parser.java:258)
at org.h2.engine.Session.prepareLocal(Session.java:578)
at org.h2.server.TcpServerThread.process(TcpServerThread.java:264)
at org.h2.server.TcpServerThread.run(TcpServerThread.java:158)
at java.lang.Thread.run(Thread.java:748)

at org.h2.engine.SessionRemote.done(SessionRemote.java:623)
at org.h2.command.CommandRemote.prepare(CommandRemote.java:85)
at org.h2.command.CommandRemote.<init>(CommandRemote.java:51)
at org.h2.engine.SessionRemote.prepareCommand(SessionRemote.java:493)
at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1247)
at org.h2.jdbc.JdbcPreparedStatement.<init>(JdbcPreparedStatement.java:76)
at org.h2.jdbc.JdbcConnection.prepareAutoCloseStatement(JdbcConnection.java:330)
at org.h2.jdbc.JdbcDatabaseMetaData.getTables(JdbcDatabaseMetaData.java:195)

Noel Grandin

unread,
Apr 13, 2018, 5:44:13 AM4/13/18
to h2-da...@googlegroups.com, Meni Hillel
there is a bug (which is fixed on master) if you mix and match different versions client and server side.

If you upgrade the client to 1.4.197, this problem should go away.

Meni Hillel

unread,
Apr 13, 2018, 3:02:13 PM4/13/18
to Noel Grandin, H2 Google Group
Thanks! Confirmed. Once both client and sever are on same version issue goes away.

Meni Hillel

unread,
Apr 16, 2018, 9:48:25 PM4/16/18
to Noel Grandin, H2 Google Group
Take it back.

Steps to reproduce:

1)  I start the server using java -cp h2-1.4.197.jar org.h2.tools.Console  -tcp -tcpAllowOthers
2) I use DBeaver client which uses the latest drivers from maven 
3) Start my application which uses the embedded file and URL AUTO_SERVER=TRUE. 

How to overcome? and when will fix be posted to maven?

Reply all
Reply to author
Forward
0 new messages