By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,004 Members | 1,253 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,004 IT Pros & Developers. It's quick & easy.

How to kill idle connections or sessions

P: n/a
Hi All
I came across a small doubt.
Suppose I have Max Connections parameter set to 200.
There are now 200 connections to the database.
Out of these 200 connections 50 are idle.
What will happen if a new user tries to connect to the database?
Whether he will receive error about MAXCONNECTIONS exceeded or he will be
allotted a connection as 50 agents are idle now?
Also how to kill those idle sessions or connections to make way for active
users?

Regards
Praveen

Mar 3 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Praveen_db2 wrote:
Hi All
I came across a small doubt.
Suppose I have Max Connections parameter set to 200.
There are now 200 connections to the database.
Out of these 200 connections 50 are idle.
What will happen if a new user tries to connect to the database?
Whether he will receive error about MAXCONNECTIONS exceeded or he will be
allotted a connection as 50 agents are idle now?
Also how to kill those idle sessions or connections to make way for active
users?


Have you actually read the responses to the other threads you started?

I think you are mixing connections and db2agent processes and we would need
to know what you have in mind to be able to give you some answers.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany
Mar 3 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.