Calculation Manager Rules Runtime Tuning

We have had a case in 11.1.2.3 Calculation Manager where I have been trying to run the business rule, running them at the Total level in the 11.1.2.3 and I had to kill the calc ran after it ran for 5 hours.

In the process of debugging,I tried at a lower level to see if at least I can get it to complete. I did test the calc at a single intersection and it ran fine in seconds but that really wasn't much good to us
as our users all enter multiple intersections through their ad hoc forms and then need to calc at an aggregate level.

While starting to dig the rootcause , I thought it might be a good idea to share what was done to tune this rule. I started with the Cube cache settings.I have shown the values above.This needs to be followed with a Essbase restart.
Also for the application, I added these two properties . In order to do this, I logged into the planning application, Administration->Application->Properties. There, I added two properties called HBR_MAX_WAIT_FOR_RULE and HBR_MONITOR_DELAY and set them to 480000 which is 8 minutes.

Post this, I carried out a complete system restart and then ran the rule. Now what took a long time was completed in 5 minutes which is a big win. 

Hyperion SmartView Tuning

While driving the 11.1.2.2 to 11.1.2.3 upgrade in my organization, I have run into various problems to which some of my earlier posts are a testament.  Today, I bring to you one from the SmartView trove. We have users who swear by Excel Addin and refuse to let go of it. There have been some instances where users are unable to retrieve large numbers on SmartView.
This was the message that was produced when the retrieve was run on private connection using 19000 url .So, It would be something like, http://ohs.servername.com:19000/aps/SmartView .

 On using the SSL link for the same, This was the error message I encountered,

                                                                                                                                                                  

Listed below are a few ways in which the tuning can help in resolving the issue. First , I would tackle the browser timeout settings by the steps shown below.

On the client machine, update/add the following registry keys:

1. Open the Registry, Start -> Run -> Regedit.

2. Locate the following section(s):

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]\

or

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Internet Settings]

3.Create the following new DWORD keys with decimal values:

ReceiveTimeout=480000
KeepAliveTimeout=180000
ServerInfoTimeout=180000

In this example, the ReceiveTimeout setting is 8 minutes. The KeepAliveTimeout and ServerInfoTimeout settings are 3 minutes. Set these to greater than the longest running request.

4. Restart the machine for the new settings to take effect.

This in my case did not seem to help. There are some more tuning parameters we can add to aps.properties file located at C:\Oracle\Middleware\EPMSystem11R1\products\Essbase\aps\bin

# Specifies values for Essbase Server network connection
# APS will try netConnectRetry times to connect to an Essbase Server.
olap.server.netRetryCount=6000
olap.server.netConnectRetry=30
olap.server.netDelay=2000
olap.server.netSocketTimeOut=20000
Also, these values need to be added to the C:\Oracle\Middleware\EPMSystem11R1\common\EssbaseJavaAPI\11.1.2.0\bin\essbase.properties  file and try making a private connection to  http://aps.servername.com:13080/aps/SmartView
Adding these values helped me resolve the large retrieve issue. This bodes well with IE9 in the case of 11.1.2.3 .

Another request that is normally made is to increase the max rows to 65000 . In order to make that change, modify the properties shown below.

# Specifies maximum rows/columns for dataquery grid. 0 value indicates no limit.
service.olap.dataQuery.grid.maxRows=65000
service.olap.dataQuery.grid.maxColumns=255
To complete the change, login to EAS and expand the provider server tree. Right click on the provider server and edit the properties .

Restart APS . That Resolves the increase row limit Issue.