Re: When does Oracle decide it's dealing with 'long ops' ?

"yas" <yasin.baskan_at_gmail.com> wrote in message news:1118146985.426445.78690_at_g43g2000cwa.googlegroups.com...
> As the documentation states: "This view displays the status of various
> operations that run for longer than 6
> seconds (in absolute time). These operations currently include many
> backup and
> recovery functions, statistics gathering, and query execution, and more
> operations
> are added for every Oracle release."
> You can also set rows in this view using the procedure
> dbms_application_info.set_session_longops.
>

It is interesting to note that there is also a parameter:

_sqlexec_progression_cost with the description: "sql execution progression monitoring cost threshold" and the default value of 1,000

It is some years since I last tested it, but I think I have a test somewhere that shows that if an SQL statement has a cost in excess of the value set for this parameter, then the statement will be tracked in v$session_longops.

This rather suggests that

    cost = 1000
equates to

    elapsed time = 6 seconds

-- 
Regards

Jonathan Lewis

http://www.jlcomp.demon.co.uk/faq/ind_faq.html
The Co-operative Oracle Users' FAQ

http://www.jlcomp.demon.co.uk/seminar.html
Public Appearances - schedule updated April 5th 2005