MaxL Crashes/Generates Empty Script When Encrypting a MaxL Script Not Working After applying Essbase 18.104.22.168.011 Patch Set Update (PSU)
Last updated on APRIL 17, 2018
Applies to:Hyperion Essbase - Version 22.214.171.124.011 and later
After applying the Essbase 126.96.36.199.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:
Essbase MaxL Shell 64-bit - Release 11.1.2 (ESB188.8.131.52.011B015)
Copyright (c) 2000, 2016, Oracle and/or its affiliates.
All rights reserved.
Public Key for Encryption: 923,2377741337
Private Key for Decryption: 1620300947,2377741337
MaxL Shell completed
When the command to encrypt the MaxL script is run, MaxL (essmsh) crashes and an empty script, file.mxls, is created: startMaxl.bat -E Test.mxl 923,2377741337
Running a previously encrypted MaxL script also crashes Maxl (essmsh): startmaxl.bat -D Test.mxls 50929109,907225463
MaxL Run from a Client System, not on Essbase Server will not crash but generates an empty script, Text.mxls.
Applied Essbase 184.108.40.206.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