Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.misc -> Re: Sequence numbers jumping
You are probably specifying CACHE = 20
in your sequence creation DDL.
If you are using designer/2000 the default
cache = 20, so when you get 1 sequence you
reserve the next 19. If you don't use them they're gone.
Recreate the sequence ith NO cache value i.e., omit CACHE completely (CACHE 1 is not valid)
Again. if you are using Des/2k you will have to edit the ddl - it will not allow null or 1 and reverts to 20.
Regards
John
FOR UTILITY PARTNERS EMPLOYMENT
OPPORTUNITIES VISIT www.utilpart.com
e-mail: jomarlen_at_aol.com
Web Site: http://members.aol.com/jomarlen/
The views expressed in this message
are those of the author and not
necessarily those of U.P. Inc.
and/or its employees.
>Subject: Re: Sequence numbers jumping
>From: "Dan Clamage" <clamage_at_mime.dw.lucent.com>
>Date: Mon, 29 Sep 1997 21:08:54 GMT
>Message-id: <01bccce2$3f9a8e20$54110b87_at_clamagent>
>
>Sounds like sequence numbers are being requested but then the (I'm assuming
>you're doing) INSERT gets rolled back (for whatever reason). Once a
>sequence number is requested by seq.NEXTVAL, it's gone, whether you really
>use it or not.
>- Dan Clamage
>
>Fenella Tan <fenella_at_voicenet.com> wrote in article
><342EF476.CB9D9919_at_voicenet.com>...
>> We're having problems with our sequence numbers. For some reason, they
>> seem to be jumping up by 20 instead of the specified increment by 1.
>> Any ideas on what may cause this ? We're using Oracle 7.3 on UNIX with
>> a Visual Basic front-end. The jumps happen intermittently. It'll work
>> (increment by 1) for a few records, and then it'll suddenly go up by 20
>> again. Appreciate any input.
>
>
>
>
>
>
>
>
Received on Tue Sep 30 1997 - 00:00:00 CDT