A minor Essbase configuration flaw introduced in Hyperion / Oracle EPM 126.96.36.199 remains present in 188.8.131.52. 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!
EPM applications help measure the business performance. This post will help you choose the best EPM solutions for your organization’s needs and objectives.
It’s 2015 and you can now establish totally respectable MS SQL DBA credibility just by mentioning you have been in the game since SQL Server version 9. You may even get the same gasps of shock from some colleagues that used to be reserved for the version 6 veterans.