Hi,
I am facing the following error when writing to a table via hibernate:
03/11/23 19:44:52 808 ERROR SqlExceptionHelper: Unique index or primary key
violation: "PRIMARY_KEY_6 ON PUBLIC.AD(ACCU_ID, TARGET_ID, REPLAY_ID)
VALUES (8, 24, 1, 7)"; SQL statement:
insert into ad (end_time, start_time,
Great, thanks!
>
>
>
--
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 h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to
Hi
I've attached test which generates the exception if MULTI_THREADED=1:
org.h2.jdbc.JdbcSQLException: Unique index or primary key violation:
"PRIMARY KEY ON PUBLIC.TRAN"; SQL statement:
INSERT INTO tran (id) values(?) [23505-193]
at
I have not tested the scenario with MVCC off because that is pretty much a
non-starter for our performance requirements.
It is kind of an odd bug because the application, the embedded h2 web
console, and the h2 shell do not have a problem with the database file.
Only other database viewers
I've been using MVCC with PageStore for years. LOBS don't work very well
(but I didn't want them in the db anyway, so we don't use LOBS). Haven't
had any issues with anything else though.
Doesn't mean bugs don't exist though.
You only get the issue with MVCC on though hey?
On 17/02/2016 1:18
At some point in the future is all I can say, not anytime soon. My
point was more that MVCC on PageStore is a dead end for us, so we're
not going to expend any effort debugging problems with it.
So if you want reliability, use PageStore without MVCC.
--
You received this message because you are
Do you know of any timelines to disable MVCC support in PageStore? I don't
see it listed in the roadmap http://www.h2database.com/html/roadmap.html
but I do see that the removal of at least one PageStore feature is being
called out.
--
You received this message because you are subscribed to
I spent some time trying to recreate the issue with a simple table set up
but was not able to. There must be something else in my database schema
that is contributing to the problem.
Interestingly enough, when I use the org.h2.tools.Shell to view my h2
database, I am able to connect to it
I'm working on creating a standalone test and will update once I have one.
Thanks!
On Tuesday, February 16, 2016 at 12:30:45 AM UTC-6, Noel Grandin wrote:
>
> Of course,it could also be that you've uncovered another tricky corner
> case - in which case we need some kind of
> standalone test
Of course,it could also be that you've uncovered another tricky corner case - in which case we need some kind of
standalone test case to be able to debug it
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop
I still get the following message using the latest version of the H2 jar
via maven:
[23505][23505] Unique index or primary key violation: "PRIMARY KEY ON
.PAGE_INDEX"; SQL statement:
I have a join table that seems to be the culprit - it uses a composite
primary key with foreign key
Hi,
I think this issue was resolved in version 1.4.179, see the changelog entry:
- Databases created with version 1.3.175 and earlier that contained
foreign keys in combination with multi-column indexes could not be opened
in some cases. This was due to a bugfix in version 1.3.176:
Hi,
I'm new to H2, and I'm working with an already existing H2 database. When I
first run H2 Console and access the database, I manage to get in. However,
after I disconnect, and try to re-access the database, the following error
occurs:
Unique index or primary key violation: PRIMARY KEY ON
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
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 sangli.mu...@gmail.com wrote:
Having the same
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. However I
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 problem
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 REFERENCES
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
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,
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.175
Provided
herehttps://groups.google.com/forum/?hl=it#!topic/h2-database/lNp80bgbvBY.
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, jack jin
Hi
I would need a reproducible test case, or the database file.
Regards, Thomas
On Thursday, May 22, 2014, jack jin super...@gmail.com 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,
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 the
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 germano.ri...@gmail.com wrote:
mano wrote
Opening it with version
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:
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
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
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 rows)
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
I test HTTP session persistence to db using latest WildFly application
server (Beta2 - SNAPSHOT, h2 1.3.173). I use this connection url
jdbc:h2:file;AUTO_SERVER=true;DB_CLOSE_ON_EXIT=FALSE,
because I want database to survive serve shutdown. Occassionally I am
facing following exception:
On 2013-10-31 13:07, Tomáš Remeš wrote:
I test HTTP session persistence to db using latest WildFly application server
(Beta2 - SNAPSHOT, h2 1.3.173). I use this
connection url jdbc:h2:file;AUTO_SERVER=true;DB_CLOSE_ON_EXIT=FALSE, because
I want database to survive serve
shutdown.
I test http session persistence to db with latest WildFly application
server (Beta2-SNAPSHOT, h2 1.3.173). I have two nodes running in my test,
where failover is tested and I use this connection url -
jdbc:h2:file;AUTO_SERVER=true. I need to use file storing, because of
server shutdown
Hi,
Actually, you are not using H2 version 1.3.173. You are using an old
version of H2 (1.3.159 according to the error code, [23505-159]). Could you
try with a newer version?
Regards,
Thomas
On Thu, Oct 31, 2013 at 12:07 PM, Tomáš Remeš tomas.re...@gmail.com wrote:
I test HTTP session
34 matches
Mail list logo
