Mr. Bort is correct if you're waiting for some resource incrementally supplying your query's needs. First I'd probably determine your sid and then select * from dba_waiters where waiting_session = <session of interest's sid>; from another session to see if there is a logical wait (aka a blocker) in your way. If that returns anything, then you can investigate the sessions listed in the column holding_session. If that returns nothing, then you're waiting for something to grind out incrementally. mwf -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Guillermo Alan Bort Sent: Thursday, April 25, 2013 9:55 AM To: rajugaru.vij@xxxxxxxxx Cc: oracle-l-freelists Subject: Re: Waiting sql You can look at the waits for the session issuing the query: v$sesstat, v$waitstat, v$statname Alternatively you can use toad's session browser. or you can run a trace and tkprof the output to get a report on what the session is waiting for. cheers Alan.- On Thu, Apr 25, 2013 at 10:28 AM, <rajugaru.vij@xxxxxxxxx> wrote: > Hi, > Iam trying to run a query, which is taking 13 to 14 minutes. Its cost > is 70. Its waiting for something. How to know for what my query is > waiting and taking so long. > > Thanks > Sent on my BlackBerryR from Vodafone-- > //www.freelists.org/webpage/oracle-l > > > -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l