On 2018/06/19 3:06 PM, Behroz Sikander wrote:
What is your opinion on the following statement that I originally posted?
"After digging into the corruption problem, we found that we use tcpAllowOthers and AUTO_SERVER=TRUE at the same time.
Due to this reason, we have sometimes "server" property in the .lock.db file and sometimes not. In all the corruption
cases, we found a .lock.db file with missing "server" property. We will remove this property soon."
Don't know. That may just mean that the crash happened during startup, before it became a server, but that doesn't mean
that it correlates with the time of corruption. Corruption unfortunately tends to show up either during
recovery/startup, or much later when a query touches the corrupted data.
If the performance of LOBs doesn't matter to you, you could try synchronizing on some single application-wide lock
object before doing any LOB work, which will minimise the chance that H2 does something wrong.
Also try confining LOB modifying SQL code to it's own JdbcConnection.
And also is there a way to set the trace file directory?
"Also, I want to enable tracing but is there a way to specify a directory for trace file? a property that I can set as
part of connection string? something similar to
Not to my knowledge.
http://h2database.com/html/features.html#trace_options
--
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.
