By Marc Schumacher on Dec 19, 2012
This week’s post will cover Essbase architecture with all its related components like Provider Services, Administration Services, Integration Services and Essbase Studio.[Read More]
Applies To: This whitepaper applies to OBIEE release 18.104.22.168, 22.214.171.124
Introduction: One of the most challenging aspects of performance tuning is knowing where to begin. To maximize Oracle® Business Intelligence Enterprise Edition performance, you need to monitor, analyze, and tune all the Fusion Middleware / BI components. This guide describes the tools that you can use to monitor performance and the techniques for optimizing the performance of Oracle® Business Intelligence Enterprise Edition components.
You can find new updated copy of OBIEE Tuning Guide Whitepaper on Support note OBIEE 11g Infrastructure Performance Tuning Guide (Doc ID 1333049.1)
Disclaimer: All tuning information stated in this guide is only for orientation, every modification has to be tested and its impact should be monitored and analyzed. Before implementing any of the tuning settings, it is recommended to carry out end to end performance testing that will also include to obtain baseline performance data for the default configurations, make incremental changes to the tuning settings and then collect performance data. Otherwise it may worse the system performance.
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.
HPCM Standard Profitability calculation scripts are named based on a documented naming convention. From 126.96.36.199.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.[Read More]
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]
This is a revised post on Reporting and Analysis. Beside the discussion of the Reporting and Analysis core component, which was part of the original post, the reporting tools WebAnalysis, Financial Reporting and Interactive Reporting, have been added to this article.[Read More]
This post is the first of a series that is going to describe the EPM System architecture per component. During the following weeks a couple of follow up posts will describe each component. Shared Services, EPMA and Calculation Manager architecture are covered by this post.[Read More]
Running into a Java out of memory error, it is very common behaviour in the field that the Java heap size will be increased. While this might help to solve a heap space out of memory error, it might not help to fix an out of memory error for the Thread Local Area (TLA). Increasing the available heap space from 1 GB to 16 GB might not even help in this situation.
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:
1. To implement HTTP compression / caching, install and configure Oracle iPlanet Web Server 7.0.x for the bi_serverN Managed Servers (refer to document http://docs.oracle.com/cd/E23943_01/web.1111/e16435/iplanet.htm)
2. On the Oracle iPlanet Web Server machine, open the file Administrator's Configuration (obj.conf) for editing. (Guidelines for modifying the obj.conf file is available at http://download.oracle.com/docs/cd/E19146-01/821-1827/821-1827.pdf)
3. Add the following lines in obj.conf file inside <Object name="default"> . </Object> and restart the Oracle iPlanet Web Server machine:
<If $path =~ '^(.*)\.(jpg|jpeg|gif|png|css|js)$'>
ObjectType fn="set-variable" insert-srvhdrs="Expires:$(httpdate($time + 864000))"
<If $path =~ '^(.*)\.(jpg|jpeg|gif|png|css|js)$'>
PathCheck fn="set-cache-control" control="public,max-age=864000"
Output fn="insert-filter" filter="http-compression" vary="false" compression-level="9" fragment_size="8096"
When working with a Hyperion Profitability and Cost Management (HPCM) Standard Costing application, there can often be a requirement to check data or allocated results using reporting tools e.g Smartview. To do this, you are retrieving data directly from the Essbase databases related to your HPCM model. For information, running reports is covered in Chapter 9 of the HPCM User documentation. The aim of this blog is to provide a quick guide to finding this data for reporting in the HPCM generated Essbase database in v188.8.131.52.x of HPCM.
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]