Hey Anita!
Thanks for the useful info.
Actually, after the stats were hanging I started querying various tables and
those queries also started hanging; queries on v$latch and a couple of others.
I finally shutdown abort and got an ORA-600 error.
I looked it up on the extremely handy ORA-600
A sort extent pool latch? That's weird. You can get the sid of the guy
holding the latch by joining v$latch.addr (or v$latchchildren if it's a
latch with children - sort extent is not) against v$latchholder.laddr.
something like
select sid from v$latch l, v$latchholder lh where l.addr =
Hi Doug!
It sounds like SMON is busy doing something else, most
likely coalescing free space or deallocating temp
segments. See metalink Note: 61997.1 SMON -
Temporary Segment Cleanup and Free Space Coalescing
While there are events that can be set to prevent smon
from coalescing or cleaning
I have a session that seems to be hung on a sql_statment.
Here is it's session_wait entry:
SID SEQ#
-- --
EVENT
P1TEXT P1
Try:
select ln.name from v$session_wait sw, v$latchname ln where sw.p2 =
ln.latch#.
Best,
George
www.pythian.com -- [EMAIL PROTECTED] -- 877-PYTHIAN
Smarter than adding another team member, Pythian has new services for
supplementing DBAs: get our help with monitoring, 24x7 on-call, daily
oops, probably only want the events that are latch frees:
select ln.name from v$session_wait sw, v$latchname ln where sw.p2 = ln.latch# and sw.event = 'latch free';
On Saturday, December 8, 2001, at 04:50 PM, George Schlossnagle wrote:
Try:
select ln.name from v$session_wait sw, v$latchname ln
Ok.. it's a sort segment latch.. any way to find out why? It's been sitting
around for over an hour ...
On Sat, 08 Dec 2001 14:35:18 -0800, you wrote:
oops, probably only want the events that are latch frees:
select ln.name from v$session_wait sw, v$latchname ln where sw.p2 =
ln.latch# and
