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

Quiz Post #2: Why you need to increase the cache size for sys.audsess$ sequence in RAC

 

Why you need to increase the cache size of sys.audsess$ sequence in RAC?

Answer:-

Background:- In oracle database every session must have an AUDSID (v$session.audsid) when the session spawns/created in database, this number is derived from a sequence called sys.audsess$ where the cache option set to 20 and noorder.

When you have an database that can provide logon storms , for example many number of users logged in first time during business start may create lot of logon storms to the database directly and these sequence value in the dictionary cache will be exhausted and it has to parse again and again another set 20 sequences cache values, which need an enqueue (SQ Lock) Enq: SQ for a long time or most of the time depend on the logon storms received.

In RAC this will become worse since the library cache/dictionary cache are global, both will have wait for this enqueue and cause dead lock or hang situation.

In order to mitigate the issue, we have to give cache clause for sequence audsess$ the bigger number especially for RAC instances (with noorder clause), say about 1000.

-Hope this helps

Comments are closed.