Oracle Database - Connection Pool

Card Puncher Data Processing


When a large number of clients run interactive Web applications, many of these sessions may be idle at a given time. The connection pooling feature enables the database server to timeout an idle session and use the connection to service an active session. The idle logical session remains open, and the physical connection is automatically reestablished when the next request comes from that session. Therefore, Web applications can allow larger numbers of concurrent users to be accommodated with existing hardware.


In the below example, the Oracle Database server has been configured with 255 connections. One of the clients has been idle past a specified amount of time. Connection pooling makes this connection available to an incoming client connection, which is connection number 256. When the idle client has more work to do, the connection is reestablished for that client with another client's idle connection.

Oracle Database Connection Pooling

Documenation / Reference

Discover More
Card Puncher Data Processing
Oracle Database - Connect Descriptor (TNS Connect String)

The Connect Descriptor (known also as TNS Connect String) is a type of connect identifier. It defines the parameters that need the Oracle Net Service to connect to a database service : the protocol...
Oracle Database Dedicated Server Processes Handling Connections Through The Connection Broker Process
Oracle Database - Pooled Server Architecture

Database resident connection pooling provides a connection pool in the database server for typical Web application usage scenarios in which an application acquires a database connection, works on it for...
Card Puncher Data Processing
Oracle Database - Service Handler

Service handlers act as connection points from the listener to an Oracle database. A service handler can be a: dispatcher in shared server configuration or a dedicated server process, or pooled....

Share this page:
Follow us:
Task Runner