Your answer is only a google away :p http://www.techonthenet.com/oracle/sequences.php
*Answer*: With respect to a sequence, the *cache* option specifies how many sequence values will be stored in memory for faster access. The downside of creating a sequence with a cache is that if a system failure occurs, all cached sequence values that have *not* be used, will be "lost". This results in a "gap" in the assigned sequence values. When the system comes back up, Oracle will cache new numbers from where it left off in the sequence, ignoring the so called "lost" sequence values. Note: To recover the lost sequence values, you can always execute an ALTER SEQUENCE command to reset the counter to the correct value. *Nocache* means that none of the sequence values are stored in memory. This option may sacrifice some performance, however, you should not encounter a gap in the assigned sequence values. On 22/01/2008, Andi Afandi <[EMAIL PROTECTED]> wrote: > > Dear all friends.., > > Mau tanya nich..., sebenarnya apa sich tujuannya ada setting cache di > sequence..? > Kalo saya pake cache., misal 20, order, interval: 1. Hasilnya nilai yg > digenerate tuh suka lompat-lompat, kadang beda 1 kadang beda 20.., jadi > solusinya saya selalu buat nocache. > > Pada saat atau bilamana kita menggunakan cache ini .....? > > > Vielen Dank > > > Afandi > > > > > > > --------------------------------- > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it > now. > > [Non-text portions of this message have been removed] > > > [Non-text portions of this message have been removed]
