Exploits in Hyperion: Hyperion Essbase – Creating a data source on a Lin...

Exploits in Hyperion: Hyperion Essbase – Creating a data source on a Lin...: In this blog, I will be talking about how to create a data source for a relational system on a Linux machine and using this data source for...

EBOOKS ONLINE: Look Smarter Than You Are with Hyperion Essbase

EBOOKS ONLINE: Look Smarter Than You Are with Hyperion Essbase

Hyperion Planning Data form Optimization

Hyperion Planning Data form Optimization

optimize data forms.

Recommendations

§  Keep dense dimensions in rows and columns.

§  Place sparse dimensions in the Page and Point of View (POV).

§  Place static dimensions in POV and hide these dimensions where not relevant to the form.

§  Place Scenario, Version, and Year dimensions in the Page wherever possible.

§  Use dynamic user variables and substitution variables as much as possible.

§  Use Run on Save and Run on Load for business rules on data forms only where business rules can complete execution within a short timeframe (say less than 30 sec.). All other business rules should be set to launch manually.

§  For Planning release 9.3.1 and later, set long-running business rules to run in the background. See the Hyperion Planning Administrator's Guide for details on these settings.

§  Limit composite data forms to two data forms where possible

§  Use the Suppress Missing Data option to skip #MISSING values from resultant data forms.

§  Split single larger data forms into multiple smaller data forms with fewer rows and columns.

§  Minimize using account annotations on data forms.

§  For Planning release 9.3 and later, enable the Mass Allocate feature on data forms only where absolutely necessary. This feature runs calculation scripts that can impact data values at intersections to which the end user may not have access.

Optimal Design Example:

Account - Rows

Time Period - Columns

Entity and other dimensions - Page/POV

Sub-optimal Design Example:

Entity - Rows

Year - Columns

Account, Time Period, and other dimensions - Page/POV

Performance Considerations :

§  The Run on Save and Run on Load calculation options place an additional demand on resources within the Essbase server for each save or load operation performed by end users. If it is necessary to use Run on Save or Run on Load, runtime prompts should be used to restrict the scope of the calculation and minimize the impact on users of the Essbase server.

§  Review the Hyperion Planning Administrator's Guide for steps that detail the execution of large calculations in batch mode. For example, you can set Planning properties to have business rules switch to background processing after a threshold that you configure. In addition, you can run business rules in batch mode using the options under Tools -->Business Rules.

§  When users access data form members that are dynamically calculated or have member formulas, an additional load is placed on the Essbase server. The impact is more acute during heavier user load.

§  The biggest impact on data from performance is the grid size. Grid size consists of the number of rows, multiplied by the number of columns. The grid size doubles if an application uses multiple currencies.

§  Adjust the number of cells retrieved to the memory on end users' client machines. To determine the number of cells, multiply the number of rows by the number of columns.

§  The Suppress Missing Blocks option for rows allows placing large sparse dimensions in rows, while providing good response time if the density of the query is low. Only blocks with data are retrieved. For example, when using this option, you can place an employee dimension consisting of thousands of members in the rows, and place the entity in the page or POV. Then, only employees of the selected entity are retrieved.

§  Using Suppress Missing Data can improve performance. Before using this feature however it is recommended that you test the impact on performance.

§  Using account annotations impacts performance. Use this option only if account annotations are required.

§  If the Supporting Detail Detection Cache reaches 75% or higher, the cache size should be increased. Enabling shared member security impacts performance. Use this option only if you want the base member's security to be based on its own security and that of all of its shared members. If this option is not enabled, users with access to the base member still have access to all of its shared members.

§  The administrator should define data forms using dynamic user variables, to narrow the data form display to the dimensionality required by users. End users can set the value for the user variable in preferences. Review the Hyperion Planning Administrator's Guide for these settings.

§  For areas with low bandwidth, it is recommended that users access Planning data forms using Smart View for Office for faster response time.

§  When Planning is first loaded, the first few requests to Planning can take longer because caches might not be loaded. It is recommended that an administrator or power user pre-load the most commonly used data forms before the general community uses the Planning server after each reboot to the Planning server.

§  It is highly recommended that administrators conduct performance tests on data forms to ensure that they meet user expectations. Data forms should be tested in both single and multi-user environments before they are deployed to production.

§  Data form definitions are cached when users log on to a Planning application. Because one cache is created for data form definitions, memory usage is not affected by the number of users viewing data forms. However, memory usage goes up if multiple users enter data in data forms at the same time.

Data Form Size Estimation:

To get a rough estimate of data form size, open the data form and select File --> Save As from the browser. The size of the .HTML file is the portion of the data form that changes based on grid size. The .JS files remain the same size and can be cached, depending on browser settings. Information such as data form definitions, pages, and .gif files are not compressed when data forms are opened and sent to the Web browser.

About Suppression

Planning follows this basic sequence to suppress information in data forms, depending on suppression settings for Suppress Missing Blocks and Suppress Missing Data.

1. First, Planning evaluates the data form definition and creates a grid to send to Essbase.

2. If Suppress Missing Blocks is selected for data form rows:

a. Planning queries Essbase to determine which members in the data form definition have data blocks. This query typically takes only a few milliseconds. (This setting is most effective for sparse dimensions, and should not be used for dense dimensions.)

b. Planning then determines which members have data blocks available in Essbase, and filters out members for which the user does not have access permissions.

3. Next, Planning constructs a grid, and sends information to Essbase to fill in the data.(The constructed grid is generally very small, so the result is returned quickly from Essbase.)

4. If Suppress Missing Data is selected, Planning suppresses data for any #MISSING data element. (This operation generally occurs quickly. However, if a large volume of data is set to #MISSING, or blocks are created but have no data, this can take some time.)

5. Planning then queries the relational database, and marks every cell to show whether it has supporting details and cell text.

6. The Web data form is then presented to the user.

UNABLE TO CREATE SPECIFIED ACTIVEX CONTROL-Smartview,

Error "UNABLE TO CREATE SPECIFIED ACTIVEX CONTROL" While Connecting to Financial Management Data Source in Excel SmartView  

---

Applies to:

1. Hyperion Financial Management - Version: 11.1.1.3.00 and later   [Release: 11.1 and later]
2. Information in this document applies to any platform.

Symptoms

The following error message is received on one user's computer, using Excel 2007: "Unable to create specified ActiveX control" while trying to connect to a Financial Management application and .

• click Data Source Manager or Active Connections (menu items) OR
• click the Connections tab (error message occurs before getting the login window)
  
  

Cause

Smartview classes are not registered properly

Solution

Re-register Smart View Addin manually using the following command:

Regsvr32 \Hyperion\SmartView\Bin\HsAddin.dll 

Example:

Regsvr32 C:\Hyperion\SmartView\Bin\HsAddin.dll 

 Procedure

• Go to StartàRun
• Paste the Above command and Click ‘OK’

Smartview Net retry count error when running calcs via Hyperion SmartView

Solution:

1. Open the Registry (Start -> Run -> Regedit)
2. Locate the following section:

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

3. Create the following new keys for DWORD with Hexadecimal values:

ReceiveTimeout and set it to 00dbba00

KeepAliveTimeout and set it to 00180000

ServerInfoTimeout and set it to 00180000


If you are still getting the timeout error your connection maybe slow and you could try increasing the KeepAliveTimout.


Note:Restart  your PC/Laptop

SmartView Error "1020011: Maximum number of rows exceeded" When Retrieving Data

SmartView Error "1020011: Maximum number of rows exceeded" When Retrieving Data

Applies to:

Hyperion Essbase - Version: 9.3.1.0.00 to 11.1.2.1.000 - Release: 9.3 to 11.1
Information in this document applies to any platform.

Symptoms

When zooming in on a parent member in SmartView or running a large query with many members, SmartView gives the following error:
"Cannot perform cube view operation. OLAP error (1020011): Maximum number of rows [5000] exceeded".

This error may also appear:

"1042017 Network error: The client or server timed out waiting to receive data using TCP/IP. Check network connections. Increase the NetRetryCount and/or NetDelay values in the essbase.cfg file. Update this file on both client and server. Restart the client and try again"

Cause

By default the Max Rows setting for Analytic Provider Services is set to 5000.

If you exceed this limit, you will see the error.

Solution

Increase the Max Rows settings by doing the following:

1. Open the \APS\bin\essbase.properties file. (Drive: \Hyperion\products\Essbase\aps\bin\ essbase.properties)
2. Locate the setting:
    service.olap.dataQuery.grid.maxRows=5000.
3. Increase the setting. Please bear in mind the Excel limits specified below.
4. Save the file and restart the Analytic Provider Services server.

§          For Excel 2003, there is a limit of 65535 rows.

§          For Excel 2007 with version 11.x of SmartView the limit is 1,048,576 rows (but this is dependent on system memory).

 Once this is updated, restart the Hyperion services.
The location of the essbase.properties file is dependent on the version of Essbase installed.  Start by going to the server with APS installed.

§         Location for version 9.3
     %HYPERION_HOME%\AnalyticProviderServices\bin directory

§         Location for version 11
     %HYPERION_HOME%\products\Essbase\aps\bin\

Note:Check These Below Things Also and set these things also

1.Right click Essbase server select Edit->Properties->Environment

2.Check Essbase properties (Essbase.cfg file) add the parameter 

          SSPROCROWLIMIT 500000
Note: Max Limit is 500000

3.Restart Essbase services

File Extension of Essbase

Application and Database File Extension of Essbase
The following table lists the file types that Essbase uses to store applications, databases, and their related artifacts
File Extension	Description
alg	Spreadsheet audit historical information
apb	Backup of application file
app	Application file, defining the name and location of the application and other application settings
arc	Archive file
atx	Spreadsheet audit transaction
chg	Outline synchronization change file
csc	Essbase calculation script
db	Database file, defining the name, location, and other database settings
dbb	Backup of database file
ddb	Partitioning definition file
ddm	Temporary partitioning file
ddn	Temporary partitioning file
esm	Essbase kernel file that manages pointers to data blocks and contains control information used for database recovery
esr	Temporary database root file
esn	Temporary Essbase kernel file
ind	Essbase index file
inn	Temporary Essbase index file
log	Server or application log
lro	LRO file linked to a data cell
lst	Cascade table of contents or list of files to back up
mxl	MaxL script file (saved in Administration Services)
ocl	Database change log
ocn	Incremental restructuring file
oco	Incremental restructuring file
olb	Backup of outline change log
olg	Outline change log
otl	Essbase outline file
otm	Temporary Essbase outline file
otn	Temporary Essbase outline file
oto	Temporary Essbase outline file
pag	Essbase database data (page) file
pan	Temporary Essbase database data (page) file
rep	Essbase report script
rul	Essbase rules file
scr	Essbase ESSCMD script
sel	Saved member select file
tct	Essbase database transaction control file that manages all commits of data and follows and maintains all transactions
tcu	Temporary database transaction control file
trg	Trigger definition file. XML (Extensible Markup Language) format
txt	Text file, such as a data file to load or a text document to link as a LRO
xcp	Exception error log
xls	Microsoft Excel File