SSO Integration Fails Between OBIEE And Essbase EPM (11.1.2)

(Doc ID 1583682.1)

Last updated on SEPTEMBER 28, 2016

Applies to:

Business Intelligence Suite Enterprise Edition - Version and later
Information in this document applies to any platform.


Multiple problems encountered when attempting to perform OBIEE integration to Essbase with Shared Services on an SQL Server database. Essbase in this case is a separate installation, not the Essbase that comes bundled with OBIEE

Attempting to follow this documentation

The first error occured trying to run this step:


 Script fails with this error

 [2013-06-17T11:10:39.230+02:00] [EPMREG] [NOTIFICATION] [EPMREG-51246]
 [oracle.EPMREG.REG] [tid: 10] [ecid: 0000JxHPLJw9XbtMweNa6G1Hjh92000000,0]
 [SRC_METHOD: getDataSource] Connection Pool EXHAUSTED.Registry will not be  able to service future requests for connection.
 [2013-06-17T11:10:39.231+02:00] [EPMREG] [ERROR] [EPMREG-11037]
 [oracle.EPMREG.REG] [tid: 10] [ecid: 0000JxHPLJw9XbtMweNa6G1Hjh92000000,0]
 [SRC_CLASS: com.hyperion.hit.registry.Registry] [SRC_METHOD: getConnection]
 An error occured when checking the status of the registry connection and a reseting it.[[  com.hyperion.hit.registry.exceptions.RegistryException: Critical Error
 Condition.Connection Leak Detected.Requests Exceeding Max Pool Size.
 com.epm.registry.util.RegPropertiesSyncUtil.main( 0)



The second error occured running this step:


 obieehesse]$ ./ removeproperty SHARED_SERVICES_PRODUCT/@applicationId.
 The ID or Tree Expression did not fetch any result.
 All IDs must be prefixed by a '#'.
 Valid expressions are like this. Please note that file and property names must be preceded by a '@' .
 Example 1 - Looking up a component - HOST/ENGINE_MANAGER
 Example 2 - Looking up a property 'Description' - HOST/ENGINE_MANAGER/@Description.
 An error occured during the operation. Detailed Message is -
 java.lang.NoClassDefFoundError: weblogic/jdbcx/db2/DB2DataSource


The third error / symptom is  invalid username or password even though OBIEE and Essbase were configured to access the same authenticator (Active Direcotory in this case)




Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms