Home » RDBMS Server » Performance Tuning » why db need kill session instantly (Oracle 10G2, RedHat Linux Enterprice6)
why db need kill session instantly [message #500551] Tue, 22 March 2011 03:52 Go to next message
Messages: 7
Registered: February 2005
Junior Member
Hello all, i have a 10G2 DB server running on RedHat Enterprisse. When the session count over 500, it will run very slow, mainly library latch waiting occuring, and the listener will stop accidentally. Restart the listener and same things happen.
If i kill some session using:
select 'kill -9 ' || p.spid from v$session s,v$process p where s.paddr=p.addr and s.program = 'AppServer.exe' and last_call_et > 30*60 and status = 'INACTIVE'
This will typically kill 200 sessions, the server will receover and runs well.
The attached pic shows that kill session at 3:10, before and after the server performance different very much.
I just wonder what's the wrong with this server? When it slow, i tried flush shared_pool but can't resolve.
  • Attachment: db_0322.jpg
    (Size: 100.08KB, Downloaded 611 times)
Re: why db need kill session instantly [message #500569 is a reply to message #500551] Tue, 22 March 2011 04:34 Go to previous messageGo to next message
Messages: 10
Registered: January 2008
Location: Singapore
Junior Member

Hi there, before you kill the sessions, have you checked
whether there are any sessions being blocked??

Mike Yeap
Re: why db need kill session instantly [message #501125 is a reply to message #500569] Sat, 26 March 2011 00:58 Go to previous message
Messages: 201
Registered: March 2005
Location: Hyderabad
Senior Member

You need to check on server capacity especially server memory and CPU capacity. There Are times where this behavior is seen when the server resources are exhaustd.
Previous Topic: sql library miss rate (2 Merged)
Next Topic: SQL Tuning ...
Goto Forum:

Current Time: Sun Aug 20 23:50:28 CDT 2017

Total time taken to generate the page: 0.01057 seconds