Enterprise Transformations, It's all About Performance Management

Yes, who uses the report scripts now, but sometimes, that is the best option; here I am not going in the debate that which is better Report Scripts, Calc Exports or MDX. This post will only concentrate on what is the best you can do with the report scripts. I myself faced a challenge in which report script was taking a couple hours to export the data, we have to bring it down to the least, here are few observations which I would like to share with all and hope this will save our fellows' time. Following them I was able to cut down the time up to 1/100X: Here are few stages where we can optimize reports: 1. Pre Report Creation Optimization, 2. Formatting Optimization, 3. Member Selection and Grouping Optimization, 4. Report Specific Optimization, Before from the time report is extracted by report extractor and displayed by report viewer, we can do be some updates to the application, this is pre report creations optimization and this will be common for all the

I have been the victim of this a couple of times, where everything was installed and configured properly without issues, however when you try to start OPMN it goes off with following error message: Starting opmn and all managed process... opmnctl startall: opmn failed to start. Error --> Process (index=X,uid=X,pid=XXXX)     failed to start a managed process after the maximum retry limit If you have something in logs, you can find the root cause and rectify the issue. But in some cases, the worst part of the issue is you wont find anything in the logs which will point you in right direction. If you look at Essbase logs, they will go in loop, they will keep on repeating the same information and there will be no error in the logs. One of the reasons: When ever you try to start OPMN it try to bind using loopback address so when loopback address is not mapped with hostname opmn fails to start. Here is a simple solution: You need to make sure there is an entry of 127.0.0