After upgrading Essbase v11.1.2.x to 11.1.2.4, Unable to Start Essbase in an Active/Passive Cluster, “Fatal Error: Failed to start ESSBASE. Lease Manager Initialization Failed.”


After applying the Essbase 11.1.2.4.0 maintenance release to 11.1.2.x in an active/passive environment, Essbase is unable to start.  The error below is shown in the Essbase.log and is generated when starting node1 via OPMN:

Fatal Error: Failed to start ESSBASE. Lease Manager Initialization Failed.

The opmn.log shows the error:

[2015-09-18T14:42:51-04:00] [opmn] [NOTIFICATION:1] [75] [ons-connect] Connection 1a;167.22.157.151;6712 connect (Connection refused) [2015-09-18T14:44:51-04:00] [opmn] [NOTIFICATION:1] [75] [ons-connect] Connection 1b;167.22.157.52;6712 connect (Connection refused)

The leasemanager.log shows the error:

2015-09-21T12:51:20.91-04:00] [ESSBASE0] [NOTIFICATION:16] [LM-9] [LM] [ecid: 1442854174685,0] [tid: 140298866731328]  Attempt to connect to database failed with error [[DataDirect][ODBC lib] Data source name not found and no default driver specified].
[2015-09-21T12:51:20.92-04:00] [ESSBASE0] [NOTIFICATION:16] [LM-9] [LM] [ecid: 1442854174685,0] [tid: 140298866731328]  Attempt to connect to database failed with error [[DataDirect][ODBC lib] Data source name not found and no default driver specified].
[2015-09-21T12:51:20.92-04:00] [ESSBASE0] [NOTIFICATION:16] [LM-1] [LM] [ecid: 1442854174685,0] [tid: 140298866731328]  Failed to acquire the lease after [6] consecutive attempts.
[2015-09-21T12:51:20.92-04:00] [ESSBASE0] [NOTIFICATION:16] [LM-16] [LM] [ecid: 1442854174685,0] [tid: 140298866731328]  Lease is being surrendered.
[2015-09-21T12:51:20.92-04:00] [ESSBASE0] [NOTIFICATION:16] [LM-11] [LM] [ecid: 1442854174685,0] [tid: 140298866731328]  Preparing to shutdown abort.
[2015-09-21T12:51:22.93-04:00] [ESSBASE0] [NOTIFICATION:16] [LM-12] [LM] [ecid: 1442854174685,0] [tid: 140298866731328]  Terminating the process.

 

This issue has been verified as the following unpublished bugs:

Bug 20411298 – RECONFIGURE ESSBASE FOR MAINTENANCE UPGRADE REMOVED SETTING FROM ESSBASE.CFG.
Bug 20405799 – RECONFIGURE ESSBASE FOR MAINTENANCE UPGRADE REMOVED FAILOVER SETTING IN OPMN.XML

 

To fix- 

After the upgrade is done, there are two options:

1.  Update the files manually with the settings from previous version, leaving the driver and ODBC information pointing to 7.1.

2.  If the files are copied from a previous version, update them with the new driver information.  For example,

In the essbase.cfg file, update the drivers to 7.1:

BPM_Oracle_DriverDescriptor “DataDirect 7.1 Oracle Wire Protocol”
BPM_DB2_DriverDescriptor “DataDirect 7.1 DB2 Wire Protocol”
;BPM_SQLServer_DriverDescriptor “DataDirect 7.1 SQL Server Native Wire Protocol”
BPM_SQLServer_DriverDescriptor “DataDirect 7.1 SQL Server Wire Protocol”
;BPM_Netezza_DriverDescriptor “NetezzaSQL”
BPM_Teradata_DriverDescriptor “Teradata”
;BPM_ORACLEBI_DriverDescriptor “Oracle BI Server 11g_OHXXXX”
BPM_ORACLEBI_DriverDescriptor “Oracle BI Server”
BPM_MySQL_DriverDescriptor “DataDirect 7.1 MySQL Wire Protocol

In the opmn.xml file, update the ODBC variables:

<variable append=”true” id=”LD_LIBRARY_PATH” value=”$EPM_ORACLE_HOME/common/ODBC-64/Merant/7.1/lib”/>

<variable id=”ODBCLIBHOME” value=”$EPM_ORACLE_HOME/common/ODBC-64/Merant/7.1/lib”/>
<variable id=”ODBCINI” value=”$EPM_ORACLE_HOME/common/ODBC-64/Merant/7.1/odbc.ini”/>
<variable id=”ODBCINST” value=”$EPM_ORACLE_HOME/common/ODBC-64/Merant/7.1/odbcinst.ini”/>

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s