RE: Session_wait

Sergey,

> This has been running for about 4 hours now. I got an SQL
> trace file, and
> looked at the execution plans. So here's the deal. There's an
> interesting
> join condition "...where A.col1=B.col1.....". However, A has
> a few hundred
> distinct values in that column, none of them being NULL, and
> B, which has a
> few hundred thousand rows, has ALL NULLs in the corresponding
> column, and
> that column is not indexed, too. That's the query where it
> sits for a couple
> of hours. Guess what the optimizer is doing (8i)? I think
> internal effects
> are secondary in this scenario. It is the production (including the

Could you determine from the SQL trace if there were updates against these indexes? That would explain the recursive SQL...

John

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: John Kanagaraj
  INET: john.kanagaraj_at_hds.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).