"enq: TX - index contention" wait during RAC Benchmark ?

  • From: "VIVEK_SHARMA" <VIVEK_SHARMA@xxxxxxxxxxx>
  • To: <oracle-l@xxxxxxxxxxxxx>
  • Date: Wed, 28 Feb 2007 20:54:02 +0530

Folks

 

During internal 2 Node RAC Benchmark OLTP Nature Transaction Runs,
following are the TOP Events from 2 Statspack.

 

Qs 1) How can the "enq: TX - index contention" wait be reduced?

Qs 2) How to identify the index undergoing contention? Do
v$session_wait.p1, p2 identify the index/Object?

 

Snapshot       Snap Id     Snap Time      Sessions Curs/Sess Comment

~~~~~~~~    ---------- ------------------ -------- ---------
-------------------

Begin Snap:        124 28-Feb-07 17:53:32       99      32.3

  End Snap:        125 28-Feb-07 18:18:08      126      27.1

   Elapsed:               24.60 (mins)

 

Top 5 Timed Events
Avg %Total

~~~~~~~~~~~~~~~~~~
wait   Call

Event                                            Waits    Time (s)
(ms)   Time

----------------------------------------- ------------ -----------
------ ------

gc buffer busy                                 625,165      11,067
18   50.0

enq: TX - index contention                      70,130       3,954
56   17.8

CPU time                                                     2,197
9.9

row cache lock                                 115,227       1,389
12    6.3

gc current block 2-way                         923,272         906
1    4.1

          -------------------------------------------------------------

 

Configuration

10gR2

Solaris 10

Veritas CFS 5.0

Banking Product

 

Will Share Statspack etc with anybody

 

Cheers

 

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended
solely for the use of the addressee(s). If you are not the intended
recipient, please notify the sender by e-mail and delete the original
message. Further, you are not to copy, disclose, or distribute this
e-mail or its contents to any other person and any such actions are
unlawful. This e-mail may contain viruses. Infosys has taken every
reasonable precaution to minimize this risk, but is not liable for any
damage you may sustain as a result of any virus in this e-mail. You
should carry out your own virus checks before opening the e-mail or
attachment. Infosys reserves the right to monitor and review the content
of all messages sent to or from this e-mail address. Messages sent to or
from this e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
        

Other related posts: