Unable to Start Essbase in an Active Passive Cluster "Fatal Error: Failed to start ESSBASE. Lease Manager Initialization Failed." (Doc ID 2059632.1)

Last updated on JANUARY 04, 2017

Applies to:

Hyperion Essbase - Version 11.1.2.4.002 and later
Information in this document applies to any platform.

Symptoms

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.

Changes

 This was an "in place upgrade" from 11.1.2.2 to 11.1.2.4 and the essbase.cfg and opmn.xml files for both nodes got overwritten.  Instead of updating, these files were copied back in from the previous version.

Cause

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