Re: Order of sequence number generation

Christian Derreth wrote:
>
> Sabarinath Nair wrote:
> >
> > Hello,
> >
> > I have a sequence created using the foolowing SQL.
> >
> > create sequence SEQ_MESSAGE_ID INCREMENT BY 1 START WITH 100 maxvalue
> > 999999999999 ORDER;
> >
> > When I use this sequence, thru a stored procedure, the sequence numbers
> > which are generated are not incrimented by 1. instead it gets increments
> > of 20. 1, 21, 42 etc...
> >
> > Does any one know how to get around this...
> >
> > Thanks
> > Sabari
>
> Dear Sabarinath,
>
> this may be due to sequence number caching. Try the NOCACHE parameter.
>
> Regards, Christian.

Or it could also be that the user obtained the number first and committed it last .....That way the later number will apper to have been first before the least number .

I usually dont like using this sequence number when I'm playing with controlled number such as check numbers and others.... coz when a user obtained them and did not commit that number is lost or if you shutdown the Db, every sequence number in your cache is gone , but they are really good when you need to supply unique keys .

Ciao !

| Joseph Sumalbag                                                                           
|
| Oracle DBA                                                                                
|
|                                                                                           
|
| The opinions expressed above are my own and doesn't 
 necessarily                           |
|reflect the opinion of any of my client company or my employer.