Issue: MaxL and Esscmd not opening from windows command line

Hi,

I am currently busy installing Oracle Hyperion EPM product suite v11.1.2.1 on VMware machines and the issues which I face while installation, I just thought of sharing here on this blog.

After installation of Essbase Server on one of the VMware machine, I found that I cant open MaxL or esscmd command from windows command line. I found that ARBORPATH and ESSBASEPATH environment variable were not set. I set it for the seesion and it worked. It can be set in the Environment Variable and then MaxL and Esscmd can be executed from windows command line.

Hope this helps you all

Keep Sharing

OraHyperion

Peroid-To-Date ( or DTS functionality) in ASO

Again I am going to give you all a link with provides you ways to implement one of the functionality which is not an Out of Box functionality of ASO cubes:

Period-To-Date functionality: This is a common requirement for Financial data to have YTD, QTD, MTD values displayed in their financial reports. BSO cubes provide an in-built DTS funtionality which caters to this requirement. However, ASO cube , being the most efficient for Financial Reporting, does not provide this functionality. However the same can be achieved in ASO cube using MDX function - PeriodsToDate.

Here is a link which shows ways to implement the same in ASO cube:
http://garycris.blogspot.com/2008/07/time-functionality.html


Enjoy ASO cube

Essbase Tricks & Tips - #1

As Essbase is so vast that we do forget some of the basics of Essbase. So I thought to start the "Tricks & Tips" series on my blog.

Disclaimer:
Please be informed that the information posted here is solely based on my knowledge and experience. Please check the content before using it - OraHyperion

Tip #1: Sometimes we face an error of Essbase server ( using command prompt or Windows Services) not getting startup.
The reason may be that the server could have got crashed while performing some calculation/restructure on the outline. Do not need to panic if this happens. Essbase engine always create a Security Backup file which contains the Users/Groups/Application/Filter information of the server in \bin folder of Essbase server. It regularly updated the .BAK file with the contents of .SEC file in the Essbase Server BIN folder.

Just delete the .SEC file and rename .BAK file to .SEC file and restart Essbase server. This re-establishes the Essbase server to the point when the Essbase server was working perfectly.