Oracle Customer Engineering & Advocacy Lab (CEAL) Blog covers Oracle Analytics Cloud, Oracle Analytics Server and...

OBIEE 11.1.1 - Increase the Number of Connection Pool in WebLogic Server

If JDBC (BI) data sources
are running out of connections to the relational database then you need to set
the maximum number of connections to high value for the following Business
Intelligence Enterprise Edition data sources:

Important Note: Reason why the default value maximum capacity
size is set to lower value is because it is important to protect database
resources. So make sure you have enough
resources on the database server (available memory is a constraint). If you increase
initial / maximum capacity to very high value, you may exceed the limit of PROCESSES
/ OPEN_CURSORS on Oracle® Database server.

Source Name
bip_datasource Initial Capacity: 0
Maximum Capacity: 50
Initial Capacity: 0
Maximum Capacity: 100

mds-owsm Initial Capacity: 0
Maximum Capacity: 50

Initial Capacity: 0
Maximum Capacity: 100

Important Note: You need to determine the optimal value for the Maximum
Capacity as part of your pre-production performance testing.
optimal values are determined then set the value of Initial Capacity equal to

value for Maximum Capacity in order to boost performance of JDBC in WebLogic
Server web applications.

Warning: Here is the example on how to size open cursors value
on Oracle® database, if you have a data source with 100 connections deployed on
2 servers and if you use default Statement Cache Size 10, you may open 2000 (100
x 2 x 10) cursors on your database server for the cached statements. You can
increase the open cursors limit in Oracle® database server.

Tip: How-to increase this value:
1. Log in to the WebLogic Server administration console.
2. Select your data source (for example “bip_datasource”), and then click on Connection Pool tab, and then Maximum Capacity.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.