I do believe that there have been reports of hangs on "cursor: pin S
wait on X" with 10.2.0.2. The best way to proceed would be to get a
system state dump and upload it to a SR. It should be able to be
identified by the trace. I believe they may be a patch/ARU for it.
On 10/24/07, Alex Gorbachev <ag_at_oracloid.com> wrote:
> Your data from ASH doesn't have anything between 10:44 and 10:53 - it
> was probably stuck as well.
>
> "os thread startup" is rather strange - problems starting new processes?
>
> And this is interesting - "cursor: pin S wait on X". Alex Fatkulin is
> hinting next to me that it *might* be new "cool" mutex that is enabled
> by default in 10.2.0.2. Disable - _kks_use_mutex_pin=false.
>
> There was a discussion on Oracle-L about it.
--
Regards,
Greg Rahn
http://structureddata.org
--
http://www.freelists.org/webpage/oracle-l
Received on Wed Oct 24 2007 - 20:16:56 CDT
