Configuring Connection Pool for Database Instance Settings

Previous TopicNext TopicContents

The connection pools create and open database connections when they are first needed. When you start the P6 EPPM server, it will allocate one or two connections for initialization routines. The server will allocate and open more connections when the pool cannot satisfy requests from the current pool. You can set the connection pool settings for:

A P6 EPPM application operation requires a database connection, so it asks the connection pool for a database connection. If the connection pool contains a connection that is not currently leased, it returns that connection. If it doesn’t have a connection available it will check to see if its current allocated count is below 50 (which is the default in the Maximum Connections setting). If the count is below 50, it will create a new database connection and open it, put it in the pool, and return it to the caller. The caller uses the connection, then releases it when they end the session.

If the pool could not allocate a connection because all 50 connections were leased, it will keep checking for the next 30 seconds (which is the default in the Lease Request Wait Timeout setting). If a connection becomes available within that 30 seconds, it will return that connection. If a connection does not become available, it will log the following error: “Error: Lease request timeout while waiting for a connection to become available. Database <dbname>” and the caller will have to try again at a later time.

To set your connection pool settings:

Note: The defaults will provide optimal performance in most environments. Change them only if you are certain a change is needed. Contact My Oracle Support for more information.

  1. Open the P6 Administrator application.
  2. In the Configurations tab, expand your configuration.
  3. Expand Database/Instance[n]/Connection Pool[aaa].
    1. In the Resize Rate field, enter the timeout period when the system will close all of its unused connections. For example, if the resize rate is 4 minutes, then every 4 minutes the connection pool will attempt to close all of its unused connections.

      The default is 4m.

      Enter anything from 4m-12h.

    2. In the Maintenance Frequency field, enter how often maintenance will run to ensure leases have not exceeded the maximum duration.

      The default is 1m.

      Enter anything from 10s-1h.

    3. In the Lease Request Wait Timeout field, enter the amount of time a request for a database connection will wait before timing out.

      If a request for a database connection times out, the user can reload the page and attempt to connect to the database again.

      The default is 30s.

      Enter anything from 5s-2h.

    4. In the Maximum Connections field, enter the maximum number of connections the server will have to the database.

      The default for Regular and Transactional is 50 and the default for Long Running is 100.

      Enter anything from 5-15000.

    5. In the Fetch Size field, enter how many rows to pull from the database and send to the application server.

      The default is 120.

    6. In the Trace SQL field, choose true to trace all SQL sent to the database.

      The default is false.

    7. In the Renewable Free Limit field, enter the minimum number of connections that leases need to be renewed.

      The default is 3.

      You can enter anything from 3-5.

    8. In the Renewable Leases field, choose true if you want connection leases renewed if database statements are completed within the MaxLeaseDuration time period. When true, the code can hold onto the connection as long as it needs, provided SQL statements finish within the MaxLeaseDuration period. When true, the connection is revoked if no SQL statements are issued within the MaxLeaseDuration period or if one statement takes longer to execute than that period.

      Choose false if you want each connection to be leased only for the MaxLeaseDuration period.

      The default for Regular is false. The default for Long Running and Transactional is true.

    9. In the Maximum Lease Durations field, enter the maximum time a database connection can be leased before it is revoked.

      The default for Regular is 2m, with a range of 5s-4h.

      The default for Long Running is 15m, with a range of 5s-6h.

      Note: During the summarization process, queries may take a long time to execute if the project has a high number of WBS nodes. If you receive timeout errors, set your Long Running maximum lease duration to at least 30 minutes.

      The default for Transactional is 10m, with a range of 5s-6h.

Related Topics

About Database Instance Settings

Configuring Driver Class and URL for Database Instance Settings

Configuring User Security for Database Instance Settings

Configuring Oracle Webcenter Content Core Capabilities Database Settings

Configuring Microsoft SharePoint in the Database Instance Settings

Configuring CMIS-Compliant Content Repository in the Database Instance Settings

Configuring the Oracle Database Content Repository

Configuring Session Settings in the Database Instance Settings

Configuring Cost Based Optimization Settings in the Database Instance Settings

Configuring Eventing in the Database Instance Settings

Configuring AIA in the Database Instance Settings

Configuring Fusion Projects Settings in the Database Instance Settings

Configuring BI Publisher in the P6 Administrator application

Configuring P6 to Connect to Oracle BPM 11g



Legal Notices
Copyright © 1999, 2015, Oracle and/or its affiliates. All rights reserved.

Last Published Wednesday, July 29, 2015

PDF Library