Yes, if you've read my post, you would've noticed that I mentioned
that there is no locking involved in so far as other sessions blocking
the session in question. As matter of fact, in some of instances
where this type of session hanging occurs, the session has an active
insert sql statement, but v$session_wait table shows that this session
has event "SQL*Net more data from client". If the session in question
is killed manually (via alter session kill and process kill), then
another session is created which will attempt exactly the same insert
query, but strangely enough, the second attempt at insert goes through
without any hanging.
srivenu_at_hotmail.com (srivenu) wrote in message news:<1a68177.0401132318.5e256b89_at_posting.google.com>...
> 1) Even though you may not have an entry in V$TRANSACTION, you can
> look at V$LOCK to see if the session has taken a DML ENQUEUE lock on
> the table.
> 2) It also helps in looking at the P1 and P2 values for the DB FILE
> SEQUENTIAL READ waits for the hanging session to find out what object
> it is trying to access.
> regards
> Srivenu
Received on Wed Jan 14 2004 - 11:41:08 CST
