Friday Feb 06, 2015
Tuesday Feb 03, 2015
By Ahmed Awan on Feb 03, 2015
Specify a Binding Host Name to have Essbase bind only to the IP address for the specified Binding Host Name. Otherwise, at startup, Essbase binds on all available IP addresses.
In EPM 22.214.171.124 / 126.96.36.199 releases, use "ESSBASESERVERHOSTNAME server_name" that identifies the host where your Essbase application process runs. The value must be a valid host name and must map to an IP address assigned to the computer. If ESSBASESERVERHOSTNAME is not specified in essbase.cfg, Essbase and the applications listen on all interfaces (IP_ANY).
For details on this refer to Essbase Tech Ref
In EPM 188.8.131.52 release, in Configure Essbase Server specifies the host name (in Binding Host Name field) to which Essbase Agent and Essbase Server bind and where an Essbase application process runs.
For details refer to http://docs.oracle.com/cd/E57185_01/epm.1112/epm_install/essbaseAgentPortPanel.html
Friday Jan 30, 2015
By Jane Story on Jan 30, 2015
Essbase BSO parallel calculation utilizes calculator cache on a per thread basis. This post is to show the relationship between using parallel calculation and calculator cache.
Tuesday Sep 09, 2014
By Keith Rosenthal on Sep 09, 2014
Using the @CURRMBR Function
Essbase provides a suite of calculation functions to facilitate the definition and development of complex member formula calculations. The @CURRMBR calculation function is especially useful with scoping and managing complex calculations. The @CURRMBR (dimension) function is used to return the name of the member currently being calculated in the specified dimension.[Read More]
Friday Jul 11, 2014
By Ann Donahue on Jul 11, 2014
The 184.108.40.206 Essbase Readme document has been updated to include a change in recommendation with regard to rebuilding versus migrating the Essbase outlines between major release upgrades. This represents a change in the upgrade process to ensure outlines take advantage of any new structures, features and functionality introduced in the major release.
Monday Jul 07, 2014
By Keith Rosenthal on Jul 07, 2014
The OLAP_MAX_CONNECTIONS property controls the maximum number of connections from Planning to Essbase. The default setting is 10, but the property can be increased to allow for more concurrent Essbase connections. The Hyperion Planning Administrator’s Guide recommends a setting of 20 for 100 users and 100 for 500 users.
Tuesday Apr 22, 2014
By Ann Donahue on Apr 22, 2014
Tuesday Jan 21, 2014
By Jane Story on Jan 21, 2014
Friday Nov 22, 2013
By Keith Rosenthal on Nov 22, 2013
Planning allows users to enter date values in Planning. For example, a start date can be entered as 11/01/2013 if the format is MM/DD/YYYY. Although the values are entered in date format, it is possible to calculate values based on dates entered.
Thursday Sep 26, 2013
By User809526-Oracle on Sep 26, 2013
Wednesday Sep 04, 2013
By Jane Story on Sep 04, 2013
ODL (Oracle Diagnostic Logging) information is recorded for both the Essbase agent and the Essbase application server. The level of the logging that is recorded can be amended if required.
These are the 2 ODL logs for Essbase:
- EssbaseAgentODLLogger is for the Essbase agent. This writes to the ESSBASE_ODL.log in MIDDLEWARE_HOME/user_projects/epmsystem1/diagnostics/logs/Essbase/Essbase
- DefSvrLogger is for the Essbase application server (ESSSVR). This writes to the <appname>_ODL.log in MIDDLEWARE_HOME/user_projects/epmsystem1/diagnostics/logs/Essbase/Essbase/app/<appname>
The level of logging for these Essbase ODL logs is controlled by the logging.xml file.
Wednesday Aug 21, 2013
By Keith Rosenthal on Aug 21, 2013
An earlier blog entry, https://blogs.oracle.com/pa/entry/planning_11_1_2_massgridstatistics, discussed the Planning 220.127.116.11 MassGridStatistics utility for displaying web form load times. Starting with the 18.104.22.168 release, MassGridStatistics has been replaced by the grid diagnostics functionality located with the Planning web interface.[Read More]
Tuesday Jul 30, 2013
Friday Jul 19, 2013
By sujata on Jul 19, 2013
After upgrading Essbase from the 11.1.1.x to 11.1.2.x releases, run through your sanity tests, such as outline dimension build updates, data loads, calculations, queries, etc. If you encounter any performance issues on the newer release of Essbase (for either ASO or BSO models) as compared to the previous release, rebuild the problematic outline on the current 11.1.2.x release. It is possibly that the outline did not migrate properly during the upgrade process.
Once you have rebuilt the outline, run through your tests again and if you still encounter performance issues, open an SR with Support.
Thursday Jul 18, 2013
By Vinay Manikyam on Jul 18, 2013
For details on configuration steps on-how to perform HFM 22.214.171.124 / OBIEE 126.96.36.199 Integration using the new ADM thin driver, download this pdf document.
A blog focused on Tips & Tricks about Oracle Business Intelligence (OBI), Oracle Exalytics and Oracle Enterprise Performance Management (EPM) products.
[Blog Admin: ahmed awan]
Popular Whitepaper Downloads
- Financial Management 188.8.131.52
- EPM 11.1.2.x - Binding Host Name to have Essbase bind only to the IP address
- Essbase BSO Parallel Calculation and Calculator Cache
- OBIEE 11.1.1 - Tuning Guide Script v1
- Adding trim functions to the column expressions in ODI
- EPM 184.108.40.206.500 - Enable HFM Thin Driver on Exlaytics server
- Getting started with Weblogic Scripting Tool for OBI
- Exalytics OVM 3.2.x - Increase Send Queue Length (txqueuelen) for VM guest (DomU) VIF
- Using the @CURRMBR Function
- Configuring OBIEE 220.127.116.11.x with Full End to End SSL