test - please ignore
--
Babette Turner-Underwood, TMI Communications
babettet_at_tmi.ca.NOSPAM (remove appropriate part to e-mail me)
Joe Kazimierczyk wrote in message <36668B89.E3030FE4_at_bms.com>...
>SNIPED means that oracle killed the session because some resource limit in
it
>the user's profile was reached (like IDLE_TIME was exceeded or something
like
>that). The session lurks around in a a sniped state until the user tries
to
>do something again. Then they get some error and the session finally goes
>away.
>
>The following query can help you find the OS pid associated with each
>session. v$process.spid is the os pid you want to kill:
>
>select
> s.username, s.osuser, s.status, s.process, p.spid, s.paddr
> from v$session s, v$process p
> where s.paddr=p.addr
>
>
>skubiszewski_at_Eisner.DECUS.Org wrote:
>
>> What does the status SNIPED mean in V$SESSION?
>>
>> Also, is there any way to associate the value of
>> process (from V$SESSION) with the actual pid on
>> the OS? I am seeing conflicting values.
>>
>> For example:
>> USERNAME PROCESS STATUS
>> -------- ------- ------
>> JONES 9742:01 SNIPED
>> SMITH 9574:01 SNIPED
>>
>> The OS (Unix) shows pids for Oracle sessions as:
>> oracle 1522 1 11:14:03 ? 0:00 oracleSID (LOCAL=NO)
>> oracle 5172 1 Nov 9 ? 0:00 oracleSID (LOCAL=NO)
>> oracle 1363 1 09:27:05 ? 0:00 oracleSID (LOCAL=NO)
>>
>> I wound up killing 1522, 5172 and 1363 because I could
>> not distinguish who was who. This had the effect of
>> killing the SMITH and JONES sessions in Oracle. I cannot
>> explain why there are 3 Unix processes and 2 Oracle
>> processes.
>>
>> Any thoughts?
>>
>> Rose
>
Received on Thu Dec 03 1998 - 10:18:24 CST
