Session_long_ops

[st2003]

I identified a user who is running a query that is taking longer than usual. I need to know how much more time is needed. I know we can use the session_long_ops to find out but what is the exact query given the SID. What are the limiatations? This is actually a job that collects data into a file.

I have a SID from v$session but when i use it in v$session_longops it returns nothing. But that SID is still showing as ACTIVE

Would appreciate immediate help
Thanks, ST2003

[dbasan]

I identified a user who is running a query that is taking longer than usual. I need to know how much more time is needed. I know we can use the session_long_ops to find out but what is the exact query given the SID. What are the limiatations? This is actually a job that collects data into a file.

I have a SID from v$session but when i use it in v$session_longops it returns nothing. But that SID is still showing as ACTIVE

Would appreciate immediate help
Thanks, ST2003

To use Session_longops you have:
-jobs running for more than 6 secs.
-to set TIMIED_STATISTICS or SQL_TRACE parameter.
-Statistics already set

If you have the above set already then you should have no troubles in seeing the columns populated!!!!!!!!

[tamilselvan]

I identified a user who is running a query that is taking longer than usual. I need to know how much more time is needed. I know we can use the session_long_ops to find out but what is the exact query given the SID. What are the limiatations? This is actually a job that collects data into a file.

I have a SID from v$session but when i use it in v$session_longops it returns nothing. But that SID is still showing as ACTIVE

Would appreciate immediate help
Thanks, ST2003

There are some bugs related to v$session_longops.
You can see the output from this view only when FULL TABLE SCAN or FAST FULL INDEX scan occur in the query plan.

Tamil

[st2003]

Thanks a lot for all your input. Really helpful.

The query started showing results eventually.

ST2003