MaxL Crashes/Generates Empty Script When Encrypting a MaxL Script Not Working After applying Essbase 11.1.2.4.011 Patch Set Update (PSU) (Doc ID 2175115.1)

Last updated on JULY 26, 2022

Applies to:

Symptoms

After applying the Essbase 11.1.2.4.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:

startMaxl.bat -gk

Essbase MaxL Shell 64-bit - Release 11.1.2 (ESB11.1.2.4.011B015)
Copyright (c) 2000, 2016, Oracle and/or its affiliates.
All rights reserved.

Public Key for Encryption: <public key string>
Private Key for Decryption: <private key string>

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 <public key string>

Running a previously encrypted MaxL script also crashes Maxl (essmsh): startmaxl.bat -D Test.mxls <public key string>

MaxL Run from a Client System, not on  Essbase Server  will not crash but generates an empty script, Text.mxls.

Changes

 Applied Essbase 11.1.2.4.011 PSU.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.