- OBIEE 11.1.1 - Advanced Usage of nqcmd command
- BI Checks with WLST - Enable debug, login and parse logs - Part 3
- OBIEE 11.1.1 - Tuning Guide Whitepaper - update available
- BI Check with WLST - SQL Datasources part 2
- BI Check with WLST - Providers and Technical users part 1
- Essbase 11.1.2.x - Web Launched EAS Console jnlp
- OBIEE 11.1.1: Load Testing Oracle Business Intelligence Enterprise Edition (OBIEE) 11g Using Oracle Load Testing (OLT) 12.x
- Calculations Using Dates Stored in Planning
- EPM Infrastructure Tuning Guide v220.127.116.11 / 18.104.22.168
Wednesday Jan 22, 2014
Tuesday Oct 15, 2013
By Ann Donahue on Oct 15, 2013
By default, Essbase will automatically backup the Essbase security file, Essbase.sec, every 300 seconds (5 minutes). Most customers find the frequency of the default backup interval overhead to be unnecessary given their security update needs. It is recommended to change the default setting before the “build” and “go-live” phases to have better Essbase.sec file backups proportionally spaced between backups and improve overhead.
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.
Tuesday Jul 30, 2013
Saturday Jul 20, 2013
By sujata on Jul 20, 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.
Friday May 17, 2013
By sujata on May 17, 2013
The steps on how to setup Essbase clustering on the 22.214.171.124 release has changed as compared to the previous releases. This document goes through how to setup Essbase clustering on Unix on the EPM 126.96.36.199 release. The information provided in this document has been taken from the EPM 188.8.131.52 Installation and Configuration Guide, which can be found here @ http://docs.oracle.com/cd/E17236_01/epm.1112/epm_install_1112200.pdf
Wednesday Apr 24, 2013
Essbase Aggregate Storage (ASO) - Incremental Outline Updates Triggers a Full or Light Outline Restructure
By Ann Donahue on Apr 24, 2013
When performing incremental updates to an Essbase Aggregate Storage (ASO) outline, depending on the nature of the incremental updates, could trigger either a full or light outline restructure.
Friday Jan 25, 2013
By Ann Donahue on Jan 25, 2013
Merge Data Slices Before Copying an Aggregate Storage (ASO) Application
When performing an Aggregate Storage (ASO) application copy, it is necessary to merge all data slices first so that all data in the ASO application will be copied properly. The current Essbase documentation does not clearly state a merge of the data is required before running an ASO application copy. An update to the Essbase documentation will be done. However, you can find the documentation update in the current Essbase 184.108.40.206.100 readme documentation. See the current Essbase 220.127.116.11.100 readme documentation under Documentation Updates: http://docs.oracle.com/cd/E17236_01/epm.1112/esb_11122100_readme.pdf
Wednesday Dec 19, 2012
Wednesday Dec 12, 2012
By Marc Schumacher on Dec 12, 2012
This is the third post on Oracle EPM System Architecture. It will cover all Financial Performance Management Applications, namely Financial Management, Essbase Analytics Link, Planning, Profitability and Cost Management, Strategic Finance and Disclosure Management. Please be aware of the fact that I also updated the previous posts on Foundation and Reporting and Analysis based on the feedback I got so far.
By Jane Story on Dec 12, 2012
HPCM Standard Profitability calculation scripts are named based on a documented naming convention. From 18.104.22.168.x, the script name = a script suffix (1 letter) + POV identifier (3 digits) + Stage Order Number (1 digit) + “_” + index (2 digits) (please see documentation for more information (http://docs.oracle.com/cd/E17236_01/epm.1112/hpm_admin/apes01.html).
This naming convention results in the name being 8 characters in length i.e. the maximum number of characters permitted calculation script names in non-unicode Essbase BSO databases. The index in the name will indicate the number of scripts per stage. In the vast majority of cases, the number of scripts generated per stage will be significantly less than 100 and therefore, there will be no issue. However, in some cases, the number of scripts generated can exceed 99.
Saturday Dec 01, 2012
Friday Nov 30, 2012
By Keith Rosenthal on Nov 30, 2012
Data recovery is typically performed by restoring data from an archive. Data added or removed since the last archive took place can also be recovered by enabling transaction logging in Essbase. Transaction logging works by writing transactions to a log store.[Read More]
Thursday Oct 11, 2012
By Ann Donahue on Oct 11, 2012
Data fragmentation naturally occurs in Essbase Block Storage (BSO) databases where there are a lot of end user data updates, incremental data loads, many lock and send, and/or many calculations executed. If an Essbase database starts to experience performance slow-downs, this is an indication that there may be too much fragmentation. See Chapter 54 Improving Essbase Performance in the Essbase DBA Guide for more details on measuring and eliminating fragmentation: http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag/daprcset.html
Fragmentation is likely to occur in the following situations:
Read/write databases that users are constantly updating data
Databases that execute calculations around the clock
Databases that frequently update and recalculate dense members
Data loads that are poorly designed
Databases that contain a significant number of Dynamic Calc and Store members
Databases that use an isolation level of uncommitted access with commit block set to zero.
Thursday Jul 19, 2012
By Ann Donahue on Jul 19, 2012
Essbase “Virtual Cube” BSO Tuning
An Essbase “virtual cube” is a specific design setup where transparent partitioning is used and consists of multiple source databases that are partitioned to a single target Block Storage (BSO) database. The single target BSO database is empty meaning contains no data. The purpose of this design setup is so that end users have one consolidated BSO cube for reporting. In some cases, the target BSO database may have different dynamic calc member formulas then the source databases. Also, the target BSO database may have more dimensions to accommodate the source databases and may have different sparse/dense configuration since source databases are tuned with data accordingly.
The Essbase Database Administration Guide mentions how to tune Essbase BSO databases that contains data; however, there is no documentation on how to tune a BSO database that contains no data like in a “virtual cube” setup.[Read More]
A blog focused on Tips & Tricks about Oracle Business Intelligence (OBI), Oracle Exalytics and Oracle Enterprise Performance Management (EPM) products.
[Blog Admin: ahmed awan]