A minor Essbase configuration flaw introduced in Hyperion / Oracle EPM 18.104.22.168 remains present in 22.214.171.124. In particular, the default “essbase.cfg” file that is automatically generated when you deploy Essbase causes all customizations you subsequently manually apply (such as calculator cache sizes, etc.) to be treated as a comment and ignored!
Here’s a typical essbase.cfg file after deploying Essbase with the default options selected within the EPM System Configurator:
Look very carefully at the end of line 11. Notice anything missing?
The MySQL driver description is missing an ending double quote character. As a result, the rest of the file is treated as a continuation of the driver description, until another double quote is found.
The solution is brutally simple: Edit the file, either on the operating system or in the EAS Console, add the ending double quote character, save, and then restart Essbase. You’re now back in business and can start adding tuning-related settings to your Essbase configuration, and now they will actually be used!
Subscribe to Our Blog
Never miss a post! Stay up to date with the latest database, application and analytics tips and news. Delivered in a handy bi-weekly update straight to your inbox. You can unsubscribe at any time.
Most people will encounter this error when their application tries to connect to an Oracle database service, but it can also be raised by one database instance trying to connect to another database service via a database link.
EPM applications help measure the business performance. This post will help you choose the best EPM solutions for your organization’s needs and objectives.