JPA Eclipselink getting wrong sequence number

Question

I'm using some Entities mapped to Oracle DB-Tables. For ID-Generation I'm using a sequence generator annotated as following:

@Id
@SequenceGenerator(name = "SEQ_RULES", sequenceName = "SEQUENZ_RULES")
@GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "SEQ_RULES")
@Column(name = "SERIALNO")
protected Long serialno;

During programm execution I make a new Instance from my Entity and want to persist this generated one. After restart of the database I'm getting wrong sequence numbers through JPA-EclipseLink, but not through the Console directly on the database.

I turned on following properties in the persistence.xml toget also the binding parameters used in the generated statements.

<properties>
  <property name="eclipselink.logging.level" value="FINE"/>
  <property name="eclipselink.logging.parameters" value="true"/>
</properties>

For example: If I generate a new instance of my entity and want to persist this one I get 2717 for serialNo and if I execute

SELECT SEQUENZ_RULES.NEXTVAL FROM DUAL

I get 2767 as nextval. The problem is that the JPA-generated serialNo must be unique, and now I stil have some datasets with this serialNo. Im getting an exception:

java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (JASON.SYS_C0084866) violated

Non Is there any caching through eclipse which is affecting the Sequence Generation or what could be the error for this?

Used Components:
GlassFish 3.1.1
EclipseLink 2.3.0.v20110604-r9504
Database: Oracle Version: Oracle Database 11g Release 11.1.0.7.0 - 64bit
Driver: Oracle JDBC driver Version: 11.2.0.1.0

Kevin Bowersox · Accepted Answer · 2013-04-30 12:23:52Z

9

When you created the sequence you specified a size to increment by. For example this sequence increments by 1.

CREATE SEQUENCE supplier_seq
  MINVALUE 1
  MAXVALUE 999999999999999999999999999
  START WITH 1
  INCREMENT BY 1
  CACHE 20;

When using the SequenceGenerator annotation in JPA you can specify an allocation size.

@Id
@SequenceGenerator(name = "SEQ_RULES", sequenceName = "SEQUENZ_RULES",
    allocationSize=1)
@GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "SEQ_RULES")
@Column(name = "SERIALNO")
protected Long serialno;

Make sure the allocation size and the increment match between JPA and the Sequence DDL.

edited Apr 30, 2013 at 12:23

answered Mar 14, 2013 at 8:52

Kevin Bowersox

94.6k19 gold badges164 silver badges198 bronze badges

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

4 Comments

MRalwasser Over a year ago

I don't think that this is the cause here - EclipseLink verifies that allocationSize and INCREMENT BY matches and will throw an exception which explicitly states that if this is not case

bjartek Over a year ago

There is an error in your example, allocationSize should be on SequenceGenerator not on GeneratedValue

Kevin Bowersox Over a year ago

@bjartek Thanks, Example has been fixed.

Sahil Chhabra Over a year ago

I used the same, but still I am getting an increment of 2 in Id instead of 1. Any idea?

whoKnows · Accepted Answer · 2015-11-10 21:30:12Z

1

Change allocationSize=1 by allocationSize=2, it is a Eclipselink bug.

edited Nov 10, 2015 at 21:30

whoKnows

9232 gold badges9 silver badges28 bronze badges

answered Nov 10, 2015 at 20:39

Juan Rodriguez

312 bronze badges

Collectives™ on Stack Overflow

JPA Eclipselink getting wrong sequence number

2 Answers 2

4 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

4 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related