RE: question about profiles/sniped sessions

We did the same thing. The story I got from Oracle is that the Oracle is still waiting until the user connects again to tell them they were previously logged off. We had to add a script that goes out and looks for sniped sessions and then issues a kill command.  

Ron Smith
Database Administration
rlsmith_at_kmg.com

-----Original Message-----
From: Koivu, Lisa [mailto:lkoivu_at_qode.com] Sent: Thursday, November 09, 2000 7:16 AM To: Multiple recipients of list ORACLE-L Subject: question about profiles/sniped sessions

Good morning -

I just implemented a profile in our production database to kill sessions idle more than one hour. Our code as it stands does not appropriately clean up after itself (yet). However, I see sniped sessions that are still sitting idle - like 2.5 hours after being 'sniped'. This concerns me, as the O/S processes are still there, too.

Can anyone tell me when these processes actually get cleaned up? I feel like I have to watch this now, and if that's the case then why use the profile in the first place?

Thanks

Lisa Rutland Koivu
Oracle Database Administrator
Qode.com
4850 North State Road 7
Suite G104
Fort Lauderdale, FL 33319

V: 954.484.3191, x174 
F: 954.484.2933 
C: 954.658.5849 

"The information contained herein does not express the opinion or position of Qode.com and cannot be attributed to or made binding upon Qode.com." Received on Thu Nov 09 2000 - 09:07:25 CST