-
SNIPED sessions
Hi Guys,
Oracle 8.1.7.3.0 on W2K.
Today, I am seeing following sessions as 'SNIPED' in our production database. They are 47.
Code:
Thread OSUser Program/Module
3656 Oracle
3156 Oracle
3216 Oracle
2536 Oracle
1524 Oracle
584 Oracle ALECDC
3220 Oracle 01@ n:\temp\OF19.tmp
3360 Oracle ALECDC
3472 Oracle
3772 Oracle
3596 Oracle ALECDC
3812 Oracle 01@ n:\temp\OF3CD.tmp
1340 Oracle
3664 Oracle ALECDC
3252 SYSTEM dbsnmp.exe
3484 Oracle ALECDC
2804 SYSTEM JDBC Thin Client
3040 SYSTEM JDBC Thin Client
3168 SYSTEM JDBC Thin Client
3296 SYSTEM JDBC Thin Client
3304 SYSTEM JDBC Thin Client
3796 Oracle 01@ n:\temp\OF50E.tmp
3788 Oracle ALECDC
3640 Oracle ALECDC
2808 SYSTEM JDBC Thin Client
2644 SYSTEM JDBC Thin Client
3292 Oracle 01@ n:\temp\OF10.tmp
3728 Oracle 01@ n:\temp\OF71C.tmp
4000 Oracle
3980 Oracle ALECDC
3576 Oracle ALECDC
3592 Oracle 01@ n:\temp\OF22.tmp
3120 SYSTEM JDBC Thin Client
3900 Oracle 01@ n:\temp\OF862.tmp
3808 SYSTEM JDBC Thin Client
3884 Oracle 01@ n:\temp\OFA50.tmp
4276 Oracle 01@ n:\temp\OFA66.tmp
3480 Oracle
1504 Oracle
1480 Oracle ALECDC
4376 Oracle 01@ n:\temp\OFC27.tmp
2336 SYSTEM JDBC Thin Client
3308 SYSTEM JDBC Thin Client
1852 Oracle ALECDC
3696 Oracle 01@ n:\temp\OFA6E.tmp
3732 SYSTEM JDBC Thin Client
4292 SYSTEM JDBC Thin Client
Some of them are one week old.
Why these sessions are not cleared by PMON?
How should I clear them out? I guess we have to use orakill command.
Thanks,
Sam
------------------------
To handle yourself, use your head. To handle others, use your heart
-
There are lot of bugs regarding this issue. The only 'workaround' at this time in these cases is to kill the OS process (Unix) or thread (NT). Yes, you can use ORAKILL. ORAKILL is run from the Command Prompt in the following syntax:
C:> orakill Sid Threadid
where: Sid is the Oracle instance to target
Thread is the thread id of the thread to kill
Threadid can be retrived from the spid column of the V$PROCESS data dictionary view.
You can use the following query to find the session threadid.
select p.spid THREADID, s.osuser, s.program
from v$process p, v$session s
where p.addr=s.paddr;
Last edited by sgodbole; 01-15-2003 at 01:32 PM.
HTH.
Shripad Godbole
OCP DBA (8,8i,9i)
"Let's document it and call it a feature."
-
Is it safe to kill any 'SNIPED' session with ORAKILL?
Thanks,
Sam
------------------------
To handle yourself, use your head. To handle others, use your heart
-
Yes. Make sure you identify correct thread or process and then kill using ORAKILL.
HTH.
Shripad Godbole
OCP DBA (8,8i,9i)
"Let's document it and call it a feature."
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|