Essbase CLI and SSL

The examination into practical uses of Essbase in the cloud continues today, with a look at a peculiar issue that crops up with the Essbase Command Line Interface (cli). Have a look at an earlier post which briefly looks at using cli with Essbase here. Oracle highly recommends securing your OAC URLs with SSL certificates for obvious reasons. Let’s look at how we log in to Essbase:

As you see, my environment is secured with an SSL certificate which needs to be “trusted”. this is done by typing “y” for “Yes”, as seen below.

This works fine, and we can proceed with our work without issue. The problem arises when we need to automate cli actions with a script.

When we run the script, we run into a prompt asking us for confirmation on trusting the certificate.

Obviously, this will not work when we need to automate our processes. This is a bug with cli that will be addressed in a future release. Thankfully, there is a workaround which is not too complicated. All we need to bypass the prompt, is to feed a “y” to the login call.

At this point, our script will work without issue.

And there you have it. A simple trick to work around the prompt suppression issue. I haven’t checked whether this is an in issue on *NIX platforms, but if it does, the “echo” or “yes” commands should work.


About Vijay Kurian

Known as the Clem Fandango of EPM consulting, Vijay Kurian has been developing enterprise solutions for companies for the last 12 years (increment years if reading post-2015). Having worked with Essbase, Planning, DRM and other assorted technologies during that time, he’s made the frankly, average decision, to write about them. He is, surprisingly, an Oracle ACE Associate. He hopes to contribute frequently to US Weekly, People and Sensible Chuckle magazines on improving reporting solutions, creating master data management systems and zzz…


  1. Thank you so much for this! My client is actually using OAC in a production environment. I didn’t understand why I would get this error. I usually only got it the first time I would use the CLI. However, today, it started each time a ran the batch script. Putting in the ECHO seemed to solve it for now.

Leave a Reply

Your email address will not be published. Required fields are marked *