[h2] Can huge delete statement execution in H2 cause JVM crash

2014-09-17 Thread Sanchand
Thomas, Suppose if I have to migrate to later version, is it enough if the latest h2 jar is used or I have to recover current h2 file and recreate using latest jar and use latest jars for accessing the h2 file. thanks -- You received this message because you are subscribed to the Google

[h2] Re: Can huge delete statement execution in H2 cause JVM crash

2014-09-16 Thread Sanchand
10, 2014 11:51:33 AM UTC+8, Sanchand wrote: In our project we execute sql files using Runscript.execute method of H2, during one such execution, there was large number of delete statement for a particular table in one of the sql file, the java utility handling the execution exited in during

[h2] Can huge delete statement execution in H2 cause JVM crash

2014-09-09 Thread Sanchand
In our project we execute sql files using Runscript.execute method of H2, during one such execution, there was large number of delete statement for a particular table in one of the sql file, the java utility handling the execution exited in during execution of that file. The utility ran

Re: [h2] Unique index or primary key violation: SYS_ID ON PUBLIC.SYS(ID) [23505-168] (using 1.3.168)

2014-08-01 Thread Sanchand
Reason for our case seems to be due to JVM crash. We use Runscript method to run SQL files with large number of inserts statements preceded by delete statement. During execution JVM is crashing, due to which dB file becomes corrupt. I tried with out of memory error also. -- You received this

[h2] Re: Unique index or primary key violation: SYS_ID ON PUBLIC.SYS(ID) [23505-168] (using 1.3.168)

2014-07-28 Thread Sanchand
Having the same problem any solution to come out of this. using h2-1.3.160.jar and Apache-Tomcat-7.0.22. When tried to run recover option and recreate database found that create statement for some tables are found twice. What could be the reason for this? On Monday, March 17, 2014