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

RAC: Cluster Interconnect performance troubleshooting – Quick reference

A quick troubleshooting reference for cluster interconnect performance in Oracle RAC to Identify network and contention issues.

a) Check for "gc cr lost blocks" wait event in Automatic Workload Repository (AWR)/sysstats.

    If found, check for these errors on the NIC:

        Dropped packets/fragments
        Buffer overflows
        Packet reassembly failures or timeouts
        TX/RX errors

    Use these commands to find any errors:

        netstat -s
        Ifconfig -a
        ORADEBUG

 b) Identify Interconnect performance from AWR.

    Under Global Cache and Enqueue Services - Workload Characteristics

        Avg global cache cr block receive time (ms): should be <=15 ms

        Global Cache and Enqueue Services - Messaging Statistics

        Avg message sent queue time on ksxp (ms): should be <1 ms

        Under Interconnect Ping Latency Stats

        Avg Latency 8K msg should be close to Avg Latency 500B msg.

c) These wait events from AWR/sysstat can indicate contention related to RAC.

        GC current block busy
        GV cr block busy
        GC current buffer busy
        GC buffer busy acquire/release

d) These wait events in the AWR indicate that there might be a Hot Block that is causing these wait events. From the AWR Segment Statistics, you can find the objects.

        Enq:TX Index Contention
        Gc buffer busy
        Gc current block busy
        Gc current split

e) This issue will be noticed if multiple sessions are inserting into a single object or are using a sequence, and the indexed column is sequentially increasing. To address the specific issues:

        Identify the indexes and Global Hash Partition them.
        Increase the Sequence Cache if ordering is not a problem. –

Thanks

Geek DBA

Comments are closed.