OBIEE Crashed When The Status Of The Managed Server, Bi

Asset ID:	1-72-2041387.1
Update Date:	2017-04-10
Keywords:

Solution Type Problem Resolution Sure

Solution 2041387.1 : OBIEE Crashed When The Status Of The Managed Server, Bi_Server1, Changed To Unknown

Applies to:

Exalytics In-Memory Machine X2-4 - Version All Versions and later
Business Intelligence Server Enterprise Edition - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

The status of the OBIEE managed server, bi_server1, changed to 'Unknown', which caused OBIEE to crash.

Cause

The demand for physical connections exceeded the number of connections allowed.

The following errors were frequently logged in the NQServer.log:

2015-07-13T05:00:06.000+00:00] [OracleBIServerComponent] [WARNING:1] [] [] [ecid: 0056Z5kRYVE9pYN5qJt1iY0001w8002C1C,0:1:1:202:6] [tid: 46d0e940] Physical connections limit is reached for connection pool "PRODDWH". Start delaying the queries.
[2015-07-13T05:01:11.000+00:00] [OracleBIServerComponent] [WARNING:1] [] [] [ecid: 0055MrXlUuG9pYN5qJt1iY0006zt00001M,0:3294] [tid: 431d3940] Physical queries backlog caused by connection shortage for connection pool "PRODDWH" is cleared
[2015-07-13T05:01:11.000+00:00] [OracleBIServerComponent] [WARNING:1] [] [] [ecid: 0056Z5kRYVE9pYN5qJt1iY0001w8002C1C,0:1:1:202:6] [tid: 46d0e940] Physical connections limit is reached for connection pool "PRODDWH". Start delaying the queries.
[2015-07-13T05:01:11.000+00:00] [OracleBIServerComponent] [WARNING:1] [] [] [ecid: 0055MrXlUuG9pYN5qJt1iY0006zt00001M,0:3297] [tid: 40885940] Physical queries backlog caused by connection shortage for connection pool "PRODDWH" is cleared

indicating that the connection pool parameters, particularly the setting for maximum connections, should be increased.

Solution

Increase the number of connections allowed for the 'Maximum connections' parameter in the Connection Pool, in the repository file.

Attachments

This solution has no attachment