No, the DB doesn't live on a shared network drive. With our current setup, the DB and all the processes using it are living on the same VM. But this will change in future.
A few questions: - When I recover my corrupted DB, and query the last row, I get Error: org.h2.jdbc.JdbcSQLException: IO Exception: "java.io.IOException: org.h2.jdbc.JdbcSQLException: IO Exception: ""Missing lob entry, block: 1225254"" [90028-176]"; "lob: null table: 34 id: 2266" [90031-176] Is this the cause of corruption? In all the corrupted databases, I see the same behavior. - Is it okay to map String to CLOB column? The column which is throwing the above error is of type CLOB in H2 but the ORM framework we use (Slick) has a type of String. So, internally String is being converted to CLOB. Thanks. On Tuesday, 19 June 2018 10:14:44 UTC+2, Noel Grandin wrote: > > > > On 2018/06/18 9:09 PM, Behroz Sikander wrote: > > 2- Within my application we connect to the database using > |jdbc:h2:tcp://<server_ip>//<path/to/db/test;AUTO_SERVER=TRUE. > > where does the DB live? on some shared network drive somewhere? > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
