Are you manually (or via a script) killing idle sessions on your database?
As a consequence, your users are getting error “ORA-00028: your session has been killed” and probably getting angry at you.
What about doing it automatically, in a much more graceful way, and be seen as a nicer DBA?
You can do this using Oracle Database Resource Manager (Resource Manager). Are you already using Resource Manager on your database? Yes? Great! No? Shame on you. Read this and put Resource Manager in place ASAP. This is a great tool for the database to manage the database resources, plus no additional licensing is needed. So go for it!
Okay, but what’s the catch?
It’s the limit max_idle_time. You can use it either on existing groups or subgroups of your plan (or subplan), or switch to “KILL” groups. With this, you can even use the same criteria you’d use for any script to perform this action. For this, you might use the parameter new_switch_group and create a different group only for those kills.
Having this option is nicer if you want to avoid killing sessions on a database. By the way, you can always switch a session for the killing group manually, instead of demanding it fill the requirements of automatic switching.
How? Quick example:
Creating new Plan Groups with MAX_IDLE_TIME:
begin dbms_resource_manager.create_plan_directive( plan => '&RM_PLAN', group_or_subplan => 'LONG_RUN', comment => 'Limit idle time to 5 minutes', max_idle_time => 300); dbms_resource_manager.create_plan_directive( plan => '&RM_PLAN', group_or_subplan => 'SHORT_RUN', comment => 'Limit idle time to 1 minute', max_idle_time => 60); end; /
And what would be the error for the user that gets the session killed?
ORA-3113 End of file on communication channel
Much nicer: Now you are a nice DBA and don’t kill sessions anymore. You automated it!
Some additional recommendations:
- Use this solution for Databases above 18.104.22.168 or 22.214.171.124, due to some known bugs:
- Bug 9523768 – IDLE SESSIONS AREN’T ACTUALLY KILLED IMMEDIATELY (affecting 126.96.36.199 to 188.8.131.52)
- Bug 13837378 – ALTER SYSTEM KILL SESSION IMMEDIATE DOES NOT KILL QC SESSIONS (184.108.40.206 to 220.127.116.11)
- Bug 8891495 – NON-IDLE SESSIONS ARE KILLED (18.104.22.168 only)
- Some MOS references on it:
- How To Automatic Kill Inactive Sessions using Resource Manager (Doc ID 1935739.1)
- Using Resource Manager to Detect and Kill Idle Sessions (Doc ID 1557657.1)
Hope this helps! You can count on Pythian to help you in implementing this or any additional needs.
Hi , I am having an issue where my invalid Sessions are 10 times more then Valid sessions and this is impacting the Connection Pool and users are not able to login …pls Advice