Re: Urgent problem : Plz help
- From: Lyndon Tiu <ltiu@xxxxxxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Thu, 19 Mar 2009 07:52:58 -0700
1) Connection pooling.
You can either have connection pooling at the DB or at the application level.
You already mentioned you do not use connection pooling at the DB level.
Looks like an application connecting to your database is not using connection
pooling either. Looks like it is opening a new connection for every query. It
also looks like it is not closing the connections properly after use.
It is good database coding practice to be using connection pooling at the
application level. That way, only a set number of connections are opened and
are kept open and reused, reducing the load on resources. This also speeds up
queries since connections don't have to be opened for each query.
Make sure to communicate that to the app developers.
2) One way to check who is opening all the connections is to use the OS command:
netstat -an
Try to find all the ip addresses connecting to the database server and track it
down and find your culprit.
--
Lyndon Tiu
--
//www.freelists.org/webpage/oracle-l
Other related posts:
