When you try to login in Essbase it will take sometime more than 10 Mins to load.
This generates stuck threads in the EAS logs.
This is due to Setting sqlnet.expire_time=10 is missing from SQLNET.ora.
The following line should be added to SQLNET.ora file:
Create an Oracle 11g database with AL32UTF8 character set encoding, and set the following database parameters:
OPEN_CURSORS – 5000
PROCESSES – 1000
SESSIONS – 2000
SESSION_CACHED_CURSORS – 200
The sqlnet.ora file in the database server should have the following setting: sqlnet.expire_time=10.
Exchange rates are stored in the Planning Relational store and refreshed to Essbase. Below is a guide to help you find exchange rates that Planning should have refreshed to Essbase in, for example, Essbase Excel addin.
You can set up the Essbase Excel addin to look at the following intersections, for example:
Months of the Fiscal year’s rates you want to see.
Select the specific Scenario (i.e. Forecast, Actuals)
Select the specific year the rates were entered to (i.e. FY02, FY03)
Specify the TOP LEVEL of Versions, Entities, or Currencies.
If the retrieval informs you that you must select a value for any required custom dimensions, make sure to select the top level member for that dimension on your spreadsheet.
In HPCM 11.1.2.x sometimes the issue happen when Hyperion Profitability and Cost Management (HPCM) service does not start.
To fix this follow the below steps.
1. Start HPCM manually to check if the problem is with the service or the configuration:
C:\Oracle\Middleware\user_projects\domains\EPMSystem\bin\ startManagedWebLogic.cmd Profitability2
2.If the above does work, then you can conclude that the issue is related to the service, in which case set the following under the window registry:
launch the registry and locate:
Change JVMOptionCount in registry from 43 to 42
Regarding HFM application servers time synchronization, each update to the application tables has a date time stamp reference. The time reference is used to determine if the data the server has in memory is current or old. Each server checks the database for changes based on the synchronization settings configured during the installation. This is covered in detail in the HFM Installation guide in the Enabling Multiple Server Support section.
When a server receives a request from a client for data it does not already have in memory then it queries the database. Data it loads from this query has a time stamp of when it was last updated and the server maintains a timestamp of when it last read from the database. When subsequent client requests for the same data come in, the server checks to see that the data it has in memory is still within the Synchronization delay setting and returns the data to the client if the delay period has not been exceed. If the time period has been exceed then the server makes another request to the database to see if the data has changed and refreshes the data and timestamp.
When a server has a data update to make then each record it needs to update is checked to verify that the records last update timestamp is older then the server’s clock. If for some reason the records timestamp is newer than the server’s clock then the update cannot proceed until the server’s clock catches up to the records last update.
When the rules are exported using EAS, it exports the BRs in a xml file, this xml files contains all the business rules, security (if you are not exporting for Calc Manager), locations etc. Now to migrate the BRs from say Production to Development environment, the location of the BRs the .xml file needs to be updated.
When exported from the Production environment the.xml will have the BR location of Production and to migrate the rules to Development, the location for development environment is needed.
1. Log into EAS console of Source Environment using an admin id,
2. Right Click on Business Rules Node,
3. Click on Export,
4. In the right hand pane you will get all the BRs listed, Click on Select All,
5. Uncheck For Calc Manager,
6. Click on Dependents,
7. Export the rules,
8. This will ask to save the BRs in a XML format save the .xml file,
9. Save As the .xml file with a different name,
10. Edit the .xml file and replace all the Old locations of BRs with the new one, the location is case sensitive and there will be two location we need to replace small case with the small one and Upper case with the Upper one, Ex: A part of exported .xml
<property class=”int” method=”setLocID” value=”41″/>
<property class=”int” method=”setLocationID” value=”41″/>
<property class=”java.lang.String” method=”setLocation” value=”ProdClusterEPPLAN”/>
<property class=”java.lang.String” method=”setUpperLocation” value=”PRODCLUSTEREPPLAN”/>
<property class=”int” method=”setCluster” value=”-1″/>
If example Destination Location is: “Planning/WDBSSAPEPMR03/EPPLAN/EPPLAN” then in the source file replace all:
ProdClusterEPPLAN with Planning/WDBSSAPEPMR03/EPPLAN/EPPLAN
PRODCLUSTEREPPLAN with PLANNING/WDBSSAPEPMR03/EPPLAN/EPPLAN
11. Save the file.
12. Log in to the destination EAS console.
13. Right click on Business Rule node.
14. Import the BRs using the modified .xml file. If you are unsure of the destination location, Create a Test Rule in the destination environment assign security, export the rule, look at the xml to find the exact location name.
today i tried to see and was curious to find the downloadable for older versions for Hyperion Essbase.
so here you goes.
In order to find Hyperion Essbase Pre-Version 9.x for downloading, please follow the steps below:
1) Log in to Oracle Software Delivery Cloud (edelivery.oracle.com)
2) Select Hyperion Performance Management and BI for Product Pack and Microsoft Windows (32-bit) for Platforms
3) Click GO
4) Click on Hyperion Performance Management and BI (Pre-Version 9.x) Media Pack for Microsoft Windows (32-bit)
5) Look for Hyperion Essbase
When retrieving data from an ASO application, the application may crash on certain retrievals.
This is due to Internal optimization being executed on MDX formulas.
If users are experiencing intermittent crashes while retrieving on an ASO application, set the following parameter in the essbase.cfg file:
FORMULAOPTLEVEL is an undocumented Essbase configuration setting that controls how MDX formulas are executed in Essbase. Essbase optimizes execution of MDX formulas by analyzing various MDX expression patterns used in a formula. The FORMULAOPTLEVEL configuration setting selectively turns off some of these optimizations. Turning off some of the optimizations may help in resolving the application crashes.
To find the size of an ASO database you can use the following MaxL command:
Query database “dbs_name” get cube_size_info;
This will display information about the input data size, aggregated data size, and number of queries tracked (when query tracking is enabled).
||Number of input-level cells in the cube
||Number of bytes used by the input-level data (approximate)
||Total number of cells in all aggregate views in the cube
||Number of bytes used by the aggregate cells (approximate)
||Number of kernel queries executed since the last time query tracking was enabled or query tracking information was reset
||Total cost of all queries executed since the last time query tracking information was reset
||Values: True or False. Tells whether user retrieval statistics are being collected for the aggregate storage database
A standard consolidation is a type of consolidation driven by the application, which uses the default consolidation and eliminations. A non-standard one is driven by the Sub Consolidate() routine in the rule file. A non-standard consolidation is commonly used by statutory applications and is written by a qualified HFM consultant.
The steps to enable Consolidation Rules in classic HFM application:
1. Extract and save application metadata.
2. Open Windows HFM Client .
3. Click on the Manage Metadata option and open the metadata file.
4. From the Metadata Item drop down field, choose Appsettings.
5. From Members section, make sure that ConsolidationRules setting is set to Y.
6. Save the file.
7. Load the modified metadata file back to the application.
Note that the setting ConsolidationRules specifies whether consolidation rules are supported. Specify one of the following values:
Y to use the rules written in the Sub Consolidate() routine in a user-defined rule.
R to derive the proportional value in the Value dimension. Note that the proportional data is not stored.
N to use the default consolidation and eliminations.
In FDMEE Archive mode is one of the option and i tried to dig more into how this is helpful for us. So below are my comments on this.
Archive Mode option is left blank – when the file is imported a copy of it is placed in the data folder. It will not have the same name as the original file, but instead an auto-generated name.
Archive Mode option is set to Copy – when the file is imported a copy of it is placed in the data folder. It will not have the same name as the original file, but instead an auto-generated name.
Archive Mode option is set to Move – when the file is imported it is moved into the data folder with a new auto-generated name.