Subscribe to Posts by Email

Subscriber Count

    699

Disclaimer

All information is offered in good faith and in the hope that it may be of use for educational purpose and for Database community purpose, but is not guaranteed to be correct, up to date or suitable for any particular purpose. db.geeksinsight.com accepts no liability in respect of this information or its use. This site is independent of and does not represent Oracle Corporation in any way. Oracle does not officially sponsor, approve, or endorse this site or its content and if notify any such I am happy to remove. Product and company names mentioned in this website may be the trademarks of their respective owners and published here for informational purpose only. This is my personal blog. The views expressed on these pages are mine and learnt from other blogs and bloggers and to enhance and support the DBA community and this web blog does not represent the thoughts, intentions, plans or strategies of my current employer nor the Oracle and its affiliates or any other companies. And this website does not offer or take profit for providing these content and this is purely non-profit and for educational purpose only. If you see any issues with Content and copy write issues, I am happy to remove if you notify me. Contact Geek DBA Team, via geeksinsights@gmail.com

Pages

18c Database : Scalable Sequences

In 18c, the sequences can be scalable. Means the sequences will have an append of extra numbers with following formula.

scalable sequence number = 6 digit scalable sequence offset number || normal sequence number

6 digit scalable sequence offset number = 3 digit instance offset number || 3 digit session offset number.

The 3 digit instance offset number is generated as [(instance id % 100) + 100]. The 3 digit session offset number is generated as [session id % 1000].

This will help to relieve the index contention and sequence cache problems in RAC since the value has large difference in values, this sequences are useful in typical loads where non primary /unique based key constraint data is not there.

As you see the ID column value of next val is showing as 101274001, instead of 1. So if we interpret the above formula

Instance 1 = 1/100 - 100.1 --> round to 101.

SID = 274

00 = Prefix to scale the sequence with three digits

1 - Original sequence number

101||274||001

You can also have extend, no extend option with scale when you create scalable sequences.

-Suresh

Comments are closed.