Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
6 replies
Subscribers
9 subscribers
Views
5603 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Oracle Sequence in CDT
anilkumark
over 8 years ago
There is a table which is using oracle sequence as a PK. I am using below annotations in XSD, the problem here is all the EMP_IDs creating in jumbling order like (1,2,3,4,13,14,5,6).
<xsd:element name="EMP_ID" type="xsd:integer">
<xsd:annotation>
<xsd:appinfo source="appian.jpa">@Id @Column(name="EMP_ID", columnDefinition="NUMBER NOT NULL") @SequenceGenerator(name="EMP_ID_SEQ_generator", sequenceName="EMP_ID_SEQ", initialValue=1) @GeneratedValue(strategy=GenerationType.SEQUENCE, generator="EMP_ID_SEQ_generator")</xsd:appinfo>
</xsd:annotation>
</xsd:element>
OriginalPostID-248506
Discussion posts and replies are publicly visible
Parents
0
felixl973
over 8 years ago
If your sequence is created with default settings its possible that your oracle sequence has the default cache of size 20. and if your oracle db application is run in a cluster, each app will have their own reserve of cache sequence IDs.
You could alter the sequence to have NOCACHE
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
felixl973
over 8 years ago
If your sequence is created with default settings its possible that your oracle sequence has the default cache of size 20. and if your oracle db application is run in a cluster, each app will have their own reserve of cache sequence IDs.
You could alter the sequence to have NOCACHE
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data