Hyperion 11.2.15 on Windows 2016 – Essbase Warning
We recently tried to apply the 11.2.15 update to an 11.2.14 environment running on Windows 2016. This should have been a supported update according to the EPM Certification matrix:
The installer ran normally with no errors. Configuration completed successfully with no errors and all looked good until we rebooted. Once we rebooted, the server never came back up. When we checked the console, it reported that the OS was corrupt. Thinking this might have been a coincidence, we rolled back to a snapshot taken just before the update. ALWAYS take backups and / or snapshots before applying an update!
This time we rebooted after installing the 11.2.15 update and before running the configuration. The server came back normally. We ran the configuration again and rebooted with the result of a corrupt OS again.
So we then rolled back to the snapshot and tried a third time, expecting for corruption, but we needed to find out what step caused the corruption. Configuring one component at a time, we found that it was the Essbase configuration that caused the OS corruption.
Since Essbase is upgraded to 21c in this update, we dug into 21c standalone documentation for a possible answer. We found that Windows 2016 is not listed as a supported OS for Essbase 21c:
Our best guess is that during configuration, the registry is updated in a manner not supported by Windows 2016, however we haven’t verified.
We’ve opened a SR with Oracle to verify this issue and to hopefully have the certification matrix updated so others don’t experience this issue. To be safe, we recommend you not apply the 11.2.15 update on a Windows 2016 server.
