OBIEE 11g - Essbase Server Fails To Start With Fatal Error
(Doc ID 2103494.1)
Last updated on SEPTEMBER 18, 2019
Applies to:Business Intelligence Server Enterprise Edition - Version 220.127.116.11.150120 and later
Information in this document applies to any platform.
You performed some modifications to the below files to change the BIPLATFORM connection string to use the Host IP instead of the HOSTNAME:
After that, starting OBIEE services succeeds for all components except for the Essbase server.
The console~AGENT~1.log file shows the following entry:
This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
Fatal Error: Security file was created in EPM mode but the current environment is in Fusion mode.. Restart Essbase using the latest backup security file, or set the ENABLESWITCHTOBACKUPFILE config setting to allow Essbase to automatically use a backup security file.
You tried the solution provided in the following document, but this did not resolve the issue:
- <Note: 1676072.1> - Unable To Start Essbase Server Installed As Part Of OBIEE 18.104.22.168.140225 Fatal Error: "Security file was created in Fusion mode but the current environment is not in Fusion mode"
Modified the database connection string in the following files:
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