|
Acording to the manuals SEQUENCE_CACHE_ENTRIES is an obsolete
parameter for 8.1.7
Ramon
----- Original Message -----
Sent: Friday, June 14, 2002 12:49
PM
Subject: Re: sequence question
while going throgh oracle manuals I found saying
number of sequence cached is governed by init parameter SEQUENCE_CACHE_ENTRIES . Does it mean that this
value should be set = 'number of sequence I want to cache' ...and what
happens if a sequence gets aged out from sequence pool . Am I going to loose
numbers ?
Did any of you guys tried caching high number
such as 10000 or 1000000 .
Thanks ,
Bp
----- Original Message -----
Sent: Friday, June 14, 2002 8:53
AM
Subject: RE: sequence question
what do you mean about losing numbers after an import/export?
Bigp
Remember that when you issue
sequence.nextval you are incrementing one value and either your
process function correct or not that number is used.
But, the more important is that if your
system crash or you issue an SHUTDOWN ABORT you will loose the sequence
numbers cached. Also you can loose numbers after an Import /
Export.
Luck,
Ramon
----- Original Message -----
Sent: Thursday, June 13, 2002 8:23
PM
Subject: sequence question
Hi List ,
I want to create a sequence which will be
used by some external process to generate some unique number . since
this sequence will be used very frequently I would prefer to cache
around 10000 numbers . Am I going to loose some numbers ?
what is SEQUENCE_CACHE_ENTRIES and how does it affect number or sequence
cached ?
Thanks ,
-Bp
|