Job Seekers   Employers
dbapool: Authors | Submissions | Contact Us
   Forgot password? | Sign up
  Home   Discussion Forum   Articles   Interview Questions   FAQs   Scripts   Rewards   Analyzer   White Papers   Blog   Certification   Downloads   Tools
 

Topic: Database Administration >> INACTIVE SESSIONS

Disclaimer: The purpose of all dbapool forums including OCP and Other Oracle Certification forums is to help each other with specific issues but not to share dump and copyrighted exam content, materials or intellectual property. You may review the entire Oracle Certification Program Candidate Agreement online Here.



  


 Title: INACTIVE SESSIONS
 Avnish  Posted: Jan 14, 2008 02:17:50 AM

 Total Post: 146
 Joined: Dec, 2007






 Hi All,
i m facing to many inactive sessions by Java thin client application.
My question is how to kill INACTIVE sessions? i applied SQLNET.EXPIRE_TIME=2 but sessions are still connected.

Thanks in Advance

Avnish

 Murtuja
Posted: Jan 14, 2008 02:33:06 AM  

 Total Post: 816
 Joined: Jan, 2006






 
You need to close connection from java application when it's close.

 Mohammed Taj
Posted: Jan 14, 2008 02:33:29 AM  

 Total Post: 746
 Joined: Jul, 2007






 
1. session status is "INACTIVE" means user is connected to database but not perform any DML/DDL statement. when user disconnect to database session will automatically closed.
NO need to kill "inactive session".

2. SQLNET.EXPIRE_TIME is use for dead connection.
suppose when user close program abnormally and session is still open in database then through SQLNET.EXPIRE_TIME parameter oracle will close that session.



 Murtuja
Posted: Jan 15, 2008 01:38:04 AM  

 Total Post: 816
 Joined: Jan, 2006






 
Hi Avnish,

Can you please confirm whether any suggestions worked for you ?

 MOH_DBA
Posted: Jan 15, 2008 12:57:13 PM  

 Total Post: 133
 Joined: Nov, 2007






 
You can use the profile parameter idle_time in Your database. but this parameter has the following issue:
PMON is responsible for sniping the sessions. It will do this periodically. HOWEVER

A session will continue to show as idle even after the idle_time for that user,
as specified in that user's profile, has expired. When the user attempts to run
a transaction against the database after the idle_time has expired, the
database will disconnect the user by terminating the session. After this, the
session will no longer show in v$session. So, even if the session appears to be idle for
a duration slightly more then your 10 minutes -- it is already "dead", it just doesn't
show as dead yet. PMON will eventually snipe the session, marking it dead in v$session.

My question to you is: did your developers instrument the code so they generate a log
that shows you what the average response times for function X, Y or Z are? (doubt it,
they never do until it is too later).

 Time Zone: EDT

  




Forum Rules & Description


Who Can Read The Forum? Any registered user or guest
Who Can Post New Topics? Any registered user
Who Can Post Replies? Any registered user




 








Get FREE Magazines

Top 10 Forum User

  Murtuja Khokhar816
  Mohammed Taj746
  Jayanta Sur479
  positive fanatic418
  Vigyan Kaushik386
  Gitesh Trivedi322
  Gopu Gopi250
  Ramesh Jois245
  neeraj sharma243
  Bishal Khetan207






oracle Mag



  About Us Advertise Terms of Use Privacy Newsletters Contact Us    

Home   Discussion Forum   FAQs  Articles  Jobs   Newsletters  Directory  Downloads 

Our Premium Sponsor
Confio Software