Essbase: Unable To Start Essbase after Migrating From Oracle Database to Exadata
(Doc ID 2731390.1)
Last updated on DECEMBER 03, 2020
Applies to:Hyperion Essbase - Version 126.96.36.199.034 and later
Information in this document applies to any platform.
Unable to start Essbase after reconfiguring EPM database connections from Oracle DB to Exadata. All EPM products start up and are functioning except Essbase. Opmnctl is used to start Essbase since Essbase Active-Passive clustering is configured.
Essbase was running without any issue before reconfiguring to Exadata. The same DB reconfiguration to Exadata worked successfully in another environment which has one Essbase server (not architected for Highly Availability).
Error message from the leasemanager_essbase log:
[ESSBASE0] [NOTIFICATION:16] [LM-9] [LM] [ecid: <ecid>] [tid: <tid>] Attempt to connect to database failed with error [[DataDirect][ODBC Oracle Wire Protocol driver][Oracle]Connection Dead. This may have occurred because the server requires Oracle Advanced Security. To enable the driver to use OAS, please use the DataIntegrityLevel and/or EncryptionLevel connect options.].
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document