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

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 m

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

Hi, I'm afraid you will need to manually edit the SQL script file. > 1.3.160 That's quite old, many bugs have been fixed since then. I suggest to upgrade to a more recent (1.3.x) version. Regards, Thomas On Saturday, July 26, 2014, Sanchand wrote: > Having the same problem any solution to

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

Hi, To re-create the database, you can use the "Recover" tool. Regards, Thomas On Sun, Jun 29, 2014 at 11:38 PM, Ravindra Gullapalli < sharewithra...@gmail.com> wrote: > Another input (might be useful) > > I did a checkout of source code of revision # 5751 and tried to generate > script. Howe

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

Another input (might be useful) I did a checkout of source code of revision # 5751 and tried to generate script. However I got the error which I posted above. Then I set the flag *retry=true* in *public void add(Session session, Row row)* method in *org.h2.index.PageDataIndex* and it generated

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

With 1.4.179 I am facing this problem Unique index or primary key violation: "PRIMARY KEY ON .PAGE_INDEX"; SQL statement: ALTER TABLE PUBLIC.TABACCOUNT ADD CONSTRAINT PUBLIC.FK_TABACCOUNT_PARENTACCOUNTNO FOREIGN KEY(PARENTACCOUNTNO) INDEX PUBLIC.FK_TABACCOUNT_PARENTACCOUNTNO_INDEX_D REFEREN

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

Hi, i am getting the error using 1.4.179 version also. Same error is coming when I try to generate script. Please help me out to get rid of this error. Ravindra. On Monday, June 2, 2014 9:46:18 PM UTC+5:30, Thomas Mueller wrote: > > Hi, > > I finally found and fixed the problem now. This proble

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

Hi, I finally found and fixed the problem now. This problem will be fixed in the next release. One workaround is to not upgrade to version 1.3.176 if the database was created with an earlier version. Another workaround is to export the database file to a SQL script and re-create it. Regards, Thom

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

Same problem. 1. The database was created in CREATE_BUILD 170, then was used with 1.3.174. I've tried using 1.4.178 on that database in Hibernate-based product - got org.h2.jdbc.JdbcSQLException: Unique index or primary key violation: "PRIMARY KEY ON .PAGE_INDEX"; SQL statement:[...] 1.3.

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

Provided here. Thanks! Il giorno giovedì 22 maggio 2014 17:43:18 UTC+2, Thomas Mueller ha scritto: > > Hi > > I would need a reproducible test case, or the database file. > > Regards, Thomas > > On Thursday, May 22, 2014, j

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

Hi I would need a reproducible test case, or the database file. Regards, Thomas On Thursday, May 22, 2014, jack jin wrote: > when I upgrade to 1.3.176,I have the same problem. the old version h2 is > works fine with the db file > > On Tuesday, May 6, 2014 5:00:52 PM UTC+8, Germano Rizzo wrote

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

when I upgrade to 1.3.176,I have the same problem. the old version h2 is works fine with the db file On Tuesday, May 6, 2014 5:00:52 PM UTC+8, Germano Rizzo wrote: > > Hi Thomas, > so your opinion is that all the db's are corrupted? The strange > thing is, they fail to open only with th

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

Hi Thomas, so your opinion is that all the db's are corrupted? The strange thing is, they fail to open only with the latest stable version. Every other version I tried works fine, and this configuration have worked in 40 installations for 3 years now, across different versions of H2. Do

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

Hi, If you are using LOCK_MODE=0;UNDO_LOG=0 then you need to be aware of the risks. See the FAQ and the documentation. Please use different email subjects for different problems. Regards, Thomas On Monday, May 5, 2014, mano wrote: > mano wrote > > Opening it with version 1.3.168 will give th

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

Same problem here. I can add that my application is widely deployed, and each instance created a db for its internal configuration. Now everyone of them is failing, so I think it's not a problem of corruption... maybe the start parameters? The jdbc url with which it was created is: jdbc:h2://a

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

Hi, same problem here. After upgrade h2-1.3.174.jar to h2-1.3.176.jar and connect to my exist db file I get to following trace: (without any executed statement, just connect) 04-10 11:50:39 database: ALTER TABLE PUBLIC.REL_USERS_RIGHTS ADD CONSTRAINT PUBLIC.REL_USERS_RIGHTS_FK_ID_USER FOREIGN K

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

Hi, I'm afraid I can't tell what the problem is. The database was created with version 1.3.168. I didn't see any temporary tables in the database file. But I'm afraid I would need a reproducible test case in order to help for this case. Regards, Thomas On Thu, Mar 27, 2014 at 8:31 PM, Dieter

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

Thoms the database is attached to the first post of this topic. Op donderdag 20 maart 2014 07:53:26 UTC+1 schreef Thomas Mueller: > > Hi, > > > I'm not using temporary tables > > I think there are some cases where Hibernate creates temporary tables, and > for some queries (those that return many

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

Hi, > I'm not using temporary tables I think there are some cases where Hibernate creates temporary tables, and for some queries (those that return many rows) the database itself creates temporary tables. If you still have the database file, could you send it to me please? I would like to analyz