OBIEE 12C - WL EM Error:Physical connections limit is reached for connection pool "Connection Pool". — Oracle Analytics

Oracle Analytics Cloud and Server

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

OBIEE 12C - WL EM Error:Physical connections limit is reached for connection pool "Connection Pool".

Received Response
51
Views
1
Comments
chillychin
chillychin Rank 6 - Analytics Lead

Sorry for creating multiple threads back to back, but I didnt want to have multiple errors in one single thread.

I am finally able to log into my new 12c installation and was able to get my 11g reports/settings into 12c as well and am in the process of validating things.

From what I can see after a quick run through of the 12c environment, I am not seeing anything unexpected.

I am seeing all the links I expect, "My Folder" in catalog, my reports all seem to render/generate ok.

I took a quick look in my weblogic enterprise manager though and noticed 2 errors (creating seperate thread for second error)

I am getting this error

[Physical connections limit is reached for connection pool "Connection Pool". Start delaying the queries.]

1
ssi
0:1:74:5
OBIS
7463c700
dcbb6724-3f2f-4d4f-9e18-fc77679b12ff-00000b3c
Physical connections limit is reached for connection pool "Connection Pool". Start delaying the queries.

file: server/Query/Execution/DbConnection/Src/SQXDCMultiThreadedPool.cpp; line: 134

**********  Task: 1. Running for (mls): 152 **********
Description: Execute Query
Repository Name: ssi
Catalog: Enrolment
Tenant:
Tenant ID: ssi
Service Name:
User: weblogic
Session ID: 0x88580000
Request ID: 0x885803e0
Logical SQL Hash:0x39669fc2
Logical SQL: [Deleted SQL for forum posting]

FETCH FIRST 65001 ROWS ONLY

I tried to google but couldnt find anything.

Is this error simply telling me that I need to increase the maximum number of connections in the connection pool?

These reports did load up quite slowly

Answers

  • Hi,

    I would say it's better to first make a quick analysis of the situation instead of just increate the number of concurrent connections as at some point this approach will start impacting something else (your DB or something else).

    So have a look at what that connection pool does, if it's the unique and single one etc. Maybe you hit that limit only in rare cases and so it isn't really something you have to care about.