Re: cursor: pin S wait on X

Hi Charles,

The mutex structures are just a latching and memory optimization. The concurrency concepts have not changed, nor have the reasons for taking an X pin. The most common match for this behaviour would be reloading a shared cursor that had been invalidated.

@   Regards,
@   Steve Adams
@   http://www.ixora.com.au/         - For DBAs
@   http://www.christianity.net.au/  - For all

Schultz, Charles wrote:
> No, but thanks for asking. The "mega-slowness" is a completely different
> issue, for which I am still befuddled.
>
> This mutex problem is something new in a test db for 10.2.0.2 (hence,
> your link to Tanel's note was helpful in that regards). Still trying to
> figure out how we arrived at 30 processes waiting on this mutex pin.
>
> -----Original Message-----
> From: Ray Stell [mailto:stellr_at_cns.vt.edu]
> Sent: Friday, April 28, 2006 12:55 PM
> To: Schultz, Charles
> Cc: oracle-l
> Subject: Re: cursor: pin S wait on X
>
>
> Be sure to post your findings. Is this at the root of your 10g
> mega-slowness?
>
>
> On Fri, Apr 28, 2006 at 12:05:22PM -0500, Schultz, Charles wrote:

>> That information is good, but I still do not know how to turn 
>> 000000A100000000 into a SID. I am reading up on askTom about bitand

--
http://www.freelists.org/webpage/oracle-l