![]() The maximum time of inactivity, in seconds, for a client after it obtains a pooled server from the pool. This parameter does not apply if the pool is at MINSIZE. After this time, the server is terminated. The maximum time, in seconds, the pooled server can stay idle in the pool. The number of session cursors to cache in each pooled server session. The number of pooled servers by which the pool is incremented if servers are unavailable when a client application request is received. When setting this parameter, ensure that there are enough pooled servers for both authentication and connections. The connection pool reserves 5% of the pooled servers for authentication, and at least one pooled server is always reserved for authentication. The maximum number of pooled servers in the pool. The minimum number of pooled servers in the pool. Table 5-2 Configuration Parameters for Database Resident Connection Pooling Parameter Name Issue the following command: SQL> EXECUTE DBMS_CONNECTION_POOL.STOP_POOL() To disable database resident connection pooling, you must explicitly stop the connection pool. (PORT=1521))(CONNECT_DATA=(SERVICE_NAME=sales)ĭisabling Database Resident Connection Pooling The following example shows a TNS connect descriptor that enables clients to connect to a database resident connection pool: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp) (HOST=myhost) The following example shows an easy connect string that enables clients to connect to a database resident connection pool: :1521/:POOLED In the client application, the connect string must specify the connect type as POOLED. Routing Client Connection Requests to the Connection Pool Any changes you make to the pool configuration are applicable on all Oracle RAC instances. In an Oracle Real Application Clusters (Oracle RAC) environment, you can use any instance to manage the connection pool. The connection pool is automatically restarted when the database instance is restarted if the pool was active at the time of instance shutdown. Once started, the connection pool remains in this state until it is explicitly stopped. Issue the following command: SQL> EXECUTE DBMS_CONNECTION_POOL.START_POOL() Start SQL*Plus and connect to the database as the SYS user. To start the connection pool, use the following steps: Starting the Database Resident Connection Pool Route the client connection requests to the connection pool, as described in "Routing Client Connection Requests to the Connection Pool". ![]() Start the database resident connection pool, as described in "Starting the Database Resident Connection Pool". ![]() To enable database resident connection pooling: To enable database resident connection pooling, you must explicitly start the connection pool. By default, this pool is created, but not started. Oracle Database includes a default connection pool called SYS_DEFAULT_CONNECTION_POOL. Enabling Database Resident Connection Pooling ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |