| status of the v$session [message #621424] |
Wed, 13 August 2014 04:48  |
muktha_22
Messages: 527
Registered: December 2009
|
Senior Member |
|
|
Hi All,
Need a small clarification for the below query.
1) I have connected a client through TOAD and executing some sample query, it still running.
2) In a SYS login I am executing the query as below
select sid,user#,username,schemaname,osuser,status from v$session
where
status!='SNIPED'
order by 3
The result shows against the client, currently executing query is "INACTIVE". But the client is not yet reached the IDLE_TIME limit.
But in documentation tells like below.
ACTIVE - Session currently executing SQL
INACTIVE - Session which is inactive and either has no configured limits or has not yet exceeded the configured limits
KILLED - Session marked to be killed
CACHED - Session temporarily cached for use by Oracle*XA
SNIPED - An inactive session that has exceeded some configured limits (for example, resource limits specified for the resource manager consumer group or idle_time specified in the user's profile). Such sessions will not be allowed to become active again.
Thanks and Regards
Muktha
|
|
|
|
|
|
|
|
|
|
| Re: status of the v$session [message #621559 is a reply to message #621555] |
Thu, 14 August 2014 05:18  |
Lalit Kumar B
Messages: 3174
Registered: May 2013
Location: World Wide on the Web
|
Senior Member |
|
|
muktha_22 wrote on Thu, 14 August 2014 15:16
And please tell me about the SNIPED session.
As documentation says, SNIPED - An inactive session that has exceeded some configured limits (for example, resource limits specified for the resource manager consumer group or idle_time specified in the user's profile). Such sessions will not be allowed to become active again.
If you want to see how resource manager consumer group is used for a query's estimated time, look at Barbara's demo here http://www.orafaq.com/forum/mv/msg/121801/333625/#msg_333625
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
