Hibernate and Oracle: Primary Key constraint violation

Question

In my web application I have multiple scheduled services which work on same entities ( like article, customer...etc). If I run a single service at time I've no problem, but when I run two services I get an error because the primary key unique constraint is violated. As primary key I use a generated Long value:

@Id
@GeneratedValue(strategy = GenerationType.AUTO)
@Column(name = "ID")
public Long getId() {
    return id;
}

Every service read data from a txt file, create its entities and every 20 entities execute a flush on hibernate session followed by a clear. Only at the end of the execution of the service the session is committed.

How can I solve?

I've already a sequence called HIBERNATE_SEQUENCE. I try to change my annotaions but I continue to get the same error. — xc93hil
– xc93hil, Commented Dec 19, 2014 at 14:40
I tried also to print the id assigned to every entity and them are all different, but the error persist! Any idea? — xc93hil
– xc93hil, Commented Dec 19, 2014 at 18:54

Maarten Winkels · Accepted Answer · 2014-12-19 14:40:03Z

3

Oracle supports only sequences for generated keys. Add a sequence to your database:

CREATE SEQUENCE ARTICLE_SEQ;

Change your annotations to:

@GeneratedValue(strategy=GenerationType.SEQUENCE, generator="articleSequence")
@SequenceGenerator(name="articleSequence", sequenceName="ARTICLE_SEQ",allocationSize=1)

It's best to use a separate sequence for each table/type.

edited Dec 19, 2014 at 14:40

answered Dec 19, 2014 at 14:14

Maarten Winkels

2,41716 silver badges16 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Koziołek · Accepted Answer · 2014-12-19 14:01:20Z

0

Create sequence in DB and use it like @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "SEQ_NAME").

answered Dec 19, 2014 at 14:01

Koziołek

2,9042 gold badges30 silver badges50 bronze badges

1 Comment

Predrag Maric Over a year ago

I think @SequenceGenerator is also needed, and generator references name of that generator, not sequence name. Sequence name is in @SequenceGenerator.

Collectives™ on Stack Overflow

Hibernate and Oracle: Primary Key constraint violation

2 Answers 2

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related