Home » SQL & PL/SQL » SQL & PL/SQL » v$session_longops
v$session_longops [message #243680] Fri, 08 June 2007 06:35 Go to next message
sanjitpandey
Messages: 16
Registered: April 2007
Junior Member
I am trying to find some facts about v$session_longops view.
Articles say that information about querry executing for more than 6 secs get inserted into this view. But in my server the query with elapsed second 0,1... also exists in this view. Can anybody tell me what is the criteria for a query to be stored in thes view?
Re: v$session_longops [message #243686 is a reply to message #243680] Fri, 08 June 2007 07:26 Go to previous messageGo to next message
Michel Cadot
Messages: 64132
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Criteria change with each version and even patchset.
Moreover, you can even yourself register your work in v$session_longops when you want.

So to answer your question, it just depends on how the developer chooses to implement his function in Oracle code.

Regards
Michel
Re: v$session_longops [message #243799 is a reply to message #243680] Sat, 09 June 2007 01:36 Go to previous messageGo to next message
gintsp
Messages: 118
Registered: February 2007
Senior Member
For some operations you can look in my paper Overview of long running operations in Oracle at http://www.gplivna.eu/papers/v$session_longops.htm

Gints Plivna
http://www.gplivna.eu
Re: v$session_longops [message #243808 is a reply to message #243680] Sat, 09 June 2007 03:24 Go to previous messageGo to next message
Michel Cadot
Messages: 64132
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Have look at Metalink note 68438.1, it lists some of the operations included in v$session_longops.
But this list changes at each version, for instance 10g adds monitoring of long rollbacks.

Actually, the Oracle internal standard is that, if an operation can be monitored (that is if the code for this is implemented), it has to be inserted in v$session_longops (actually x$ksulop) if the estimated or current cost of the operation exceeds the value of the hidden parameter _sqlexec_progression_cost (default is 1000, 0 means do not record).

Regards
Michel
Re: v$session_longops [message #244204 is a reply to message #243680] Mon, 11 June 2007 23:35 Go to previous message
sanjitpandey
Messages: 16
Registered: April 2007
Junior Member
Thank you everybody. I got answer to my question.

Thanks again.
Previous Topic: query help need, PLEASE
Next Topic: Condition ending with (+) ? What is mean?
Goto Forum:
  


Current Time: Wed Dec 07 16:28:09 CST 2016

Total time taken to generate the page: 0.29855 seconds