Re: cursor: pin S wait on X
- From: pbairagi@xxxxxxxxx
- To: Rui.Amaral@xxxxxxxxxxxxxxxx,"'Joel.Patterson@xxxxxxxxxxx'" <Joel.Patterson@xxxxxxxxxxx>,"grzegorzof@xxxxxxxxxx" <grzegorzof@xxxxxxxxxx>
- Date: Thu, 11 Nov 2010 16:23:32 +0000
Forwarding.
Sent on my BlackBerry® from Vodafone
-----Original Message-----
From: "Amaral, Rui" <Rui.Amaral@xxxxxxxxxxxxxxxx>
Sender: oracle-l-bounce@xxxxxxxxxxxxx
Date: Tue, 9 Nov 2010 15:01:03
To: 'Joel.Patterson@xxxxxxxxxxx'<Joel.Patterson@xxxxxxxxxxx>;
grzegorzof@xxxxxxxxxx<grzegorzof@xxxxxxxxxx>
Reply-To: Rui.Amaral@xxxxxxxxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx<oracle-l@xxxxxxxxxxxxx>
Subject: RE: cursor: pin S wait on X
There were some bugs on 11.1.0.7 on linux (a couple that hit me).
Rui Amaral
Database Administrator
ITS - SSG
TD Bank Financial Group
220 Bay St., 11th Floor
Toronto, ON, CA, M5K1A2
(bb) (647) 204-9106
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Joel.Patterson@xxxxxxxxxxx
Sent: Tuesday, November 09, 2010 2:59 PM
To: grzegorzof@xxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: RE: cursor: pin S wait on X
10.2.0.4. We plan on upgrading to 11gR2. (solaris 10)
I saw some bugs pertaining to 10.2.0.3...
Joel Patterson
Database Administrator
904 727-2546
-----Original Message-----
From: Grzegorz Goryszewski [mailto:grzegorzof@xxxxxxxxxx]
Sent: Tuesday, November 09, 2010 2:45 PM
To: Patterson, Joel
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: cursor: pin S wait on X
W dniu 2010-11-09 20:26, Joel.Patterson@xxxxxxxxxxx pisze:
> This question is somewhat associated with my lsuosstats global area latch
> question recently posted.
>
> We were running a load test and so many of the queries where probably doing
> the exact same thing. So the event "cursor: pin S wait on X" which bubbled
> to the top.
>
> > From Tanel Poders web site: "A mutex differs from a latch in that there
> > would be many more requestors backed up on a latch, whereas a mutex in this
> > case protects just one cursor."
> Since this was a test, I am assuming that this is nothing to be concerned
> about now, but if I were to become concerned about it, does anyone know how
> they could approach this event specifically? Is there anything we can do
> about it now - because we are testing?
Hi,
which database version You talking about ?
There was some bugs related to that mutex .
Regards.
Greg
--
//www.freelists.org/webpage/oracle-l
NOTICE: Confidential message which may be privileged. Unauthorized
use/disclosure prohibited. If received in error, please go to www.td.com/legal
for instructions.
AVIS : Message confidentiel dont le contenu peut être privilégié.
Utilisation/divulgation interdites sans permission. Si reçu par erreur, prière
d'aller au www.td.com/francais/avis_juridique pour des instructions.
--
//www.freelists.org/webpage/oracle-l
Other related posts:
