Blacklisted Connection Pool (OBIEE 11.1.1.5)

This error, detectable in the log sawserver, appears when there is a problem with the initialization block of a variable. In my case, for example, OBI had to initialize a substitution variable from Essbase, but the variable was removed from Essbase server.

To solve this problem you need to verify that the initialization block is valid in that, the first error in the initialization phase, OBI puts in blacklist the entire connection pool. Accordingly will not be processed all the following variables associated with that connection.

For further we can refer to the documentation:

http://docs.tpu.ru/docs/oracle/en/fmw/11.1.1.6.0/doc.1111/e14771/biee.htm

41.15.7.7 Initialization Block Failure at Server Start-Up Causes Connection Pool to be Blacklisted

Impacted Releases: 11.1.1.5

During Oracle BI Server start-up, if an initialization block fails for a particular connection pool, no more initialization blocks using that connection pool are processed. Instead, the connection pool is blacklisted and subsequent initialization blocks for that connection pool are skipped. This behavior ensures that the Oracle BI Server starts in a timely manner, even when a connection pool has a large number of associated initialization blocks or variables.

If this occurs, a message similar to the following appears in the server log:

[OracleBIServerComponent] [ERROR:1] [43143] Blacklisted connection pool conn_pool_name

If you see this error, check the initialization blocks for the given connection pool to ensure that they are correct.