Re: Mutex contention on database server

Hi Yong,

   I think you are right.
You NAIL the problem in my work. (Although, there might be more than 1 problem in that application).
I think those application written by developer is NOT using bind variables.

Thank you so much for your HINT in the V$session_wait and the P2.

Dominica

yong..._at_yahoo.com wrote:
> Hi, Dominica,
>
> Virtual Adrian is a Solaris performance monitoring tool written by
> Adrian Cockcroft. That mutex contention field comes from `mpstat`
> output smtx column, defined as "spins on mutexes (lock not acquired
on
> first try)". As Jonathan pointed out, these spins roughly translate
to
> latch acquisition inside Oracle. The only thing your UNIX system
admin
> can do may be replace the CPUs with faster ones (instead of adding
more
> CPUs). But the root cause of the problem, if it's a problem at all,
is
> tuning Oracle. For instance, if you see frequent "latch free" wait in
> v$session_wait and p2 indicates library cache, then make sure to use
> bind variables, etc.
>
> Mutex contention is not related to semaphore setting in /etc/system.
>
> Yong Huang
Received on Sun May 01 2005 - 01:15:13 CDT