MaxL Crashes/Generates Empty Script When Encrypting a MaxL Script Not Working After applying Essbase 126.96.36.199.011 Patch Set Update (PSU)
Last updated on DECEMBER 01, 2016
Applies to:Hyperion Essbase - Version 188.8.131.52.011 and later
After applying the Essbase 184.108.40.206.011 PSU, there are multiple issues when trying to encrypt a MaxL script depending on where MaxL is run from:
- MaxL Crashes
- Generating an empty encrypted script
- Encrypted statements not decoded
The following examples are from a Windows environment.
MaxL run on the Essbase Server from the \Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\bin directory:
Generate keys is successful:
MaxL Run from a Client System, not on Essbase Server will not crash but generates an empty script, Text.mxls.
Applied Essbase 220.127.116.11.011 PSU.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms