Friday Jan 31, 2014

OBIEE 11.1.1 - Tuning Guide Whitepaper - update available

New updates have been made to the OBIEE "Best Practices Guide for Infrastructure Tuning" whitepaper. This updated whitepaper is for 11g Release 1 (11.1.1.6, 11.1.1.7) and can be downloaded from the My Oracle Support knowledge article: Doc ID 1333049.1

The new revised document contains the following useful new and/or updated tuning items:

  • Optimized JVM switches for Oracle JRockit / Sun JVM / IBM JVM etc
  • New tuning parameters settings / values for JavaHost / OPIS / OBIS components.
  • Improved BIEE / platform performance monitoring techniques.
  • IBM WebSphere tuning parameters.
  • More WebLogic Server tuning parameters.
  • Windows Server 2012 tuning parameters.
  • New optimized Linux / AIX tuning parameters.
  • Additional Essbase ASO tuning parameters.
  • libOVD authenticator search tuning
    And many more….

Thursday Oct 17, 2013

EPM Infrastructure Tuning Guide v11.1.2.2 / 11.1.2.3

Applies To: This edition applies to only 11.1.2.2, 11.1.2.3.

One of the most challenging aspects of performance tuning is knowing where to begin. To maximize Oracle EPM System performance, all components need to be monitored, analyzed, and tuned. This guide describe the techniques used to monitor performance and the techniques for optimizing the performance of EPM components.

TOP TUNING RECOMMENDATIONS FOR EPM SYSTEM:

Performance tuning Oracle Hyperion EPM system is a complex and iterative process. To get you started, we have created a list of recommendations to help you optimize your Oracle Hyperion EPM system performance.

This chapter includes the following sections that provide a quick start for performance tuning Oracle EPM products. Note these performance tuning techniques are applicable to nearly all Oracle EPM products such as Financial PM Applications, Essbase, Reporting and Foundation services.

1. Tune Operating Systems parameters.
2. Tune Oracle WebLogic Server (WLS) parameters.
3. Tune 64bit Java Virtual Machines (JVM).
4. Tune 32bit Java Virtual Machines (JVM).
5. Tune HTTP Server parameters.
6. Tune HTTP Server Compression / Caching.
7. Tune Oracle Database Parameters.
8. Tune Reporting And Analysis Framework (RAF) Services.
9. Tune Oracle ADF parameters.

Click to Download the EPM 11.1.2.3 Infrastructure Tuning Whitepaper (Right click or option-click the link and choose "Save As..." to download this pdf file)

Tuesday Oct 15, 2013

Essbase Best Practice: Essbase Security File Auto Backup Intervals

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.

[Read More]

Friday Mar 08, 2013

Using Essbase Query Governors with Forms Containing User Variables

Many Planning customers today are designing forms containing user variables. User variables allow the user to customize the information presented on a form based on the user’s security. In addition, the number of forms maintained in the application is reduced since multiple versions of the same form having different dimension members do not need to be created.

[Read More]

Wednesday Dec 12, 2012

HPCM 11.1.2.2.x - HPCM Standard Costing Generating >99 Calc Scipts

HPCM Standard Profitability calculation scripts are named based on a documented naming convention. From 11.1.2.2.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]

Saturday Dec 01, 2012

Essbase Analytics Link (EAL) - Performance of some operation of EAL could be improved by tuning of EAL Data Synchronization Server (DSS) parameters

Generally, performance of some operation of EAL (Essbase Analytics Link) could be improved by tuning of EAL Data Synchronization Server (DSS) parameters.

a. Expected that DSS machine will be 64-bit machine with 4-8 cores and 5-8 GB of RAM dedicated to DSS.

b. To change DSS configuration - open EAL Configuration Tool on DSS machine.

 

[Read More]

Wednesday Oct 31, 2012

Error java.lang.OutOfMemoryError: getNewTla using Oracle EPM products

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.


[Read More]

Thursday Oct 11, 2012

Essbase BSO Data Fragmentation

Essbase BSO Data Fragmentation

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.
[Read More]

Friday Aug 24, 2012

Performance of Run Time Prompt Limits in Calc Manager

When using run time prompt limits in Calc Manager, performance is faster when using Essbase member list functions that are explicitly defined and accessed directly in Planning.[Read More]

Changing the Planning Language

If Essbase is set to a language other than English, the language should be changed in Planning to improve the stability of the Planning JVM during periods of heavy usage. In order to change the Planning language, open the setCustomParamsPlanning.bat (Windows) or SetCustomParamsPlanning.sh (Unix) located in the MIDDLEWARE_HOME/user_projects/epmsystem1/bin folder.[Read More]

Thursday Jul 19, 2012

Essbase “Virtual Cube” BSO Tuning

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]

Wednesday Jun 27, 2012

HPCM 11.1.2.x - Outline Optimisation for Calculation Performance

When an HPCM application is first created, it is likely that you will want to carry out some optimisation on the HPCM application’s Essbase outline in order to improve calculation execution times. There are several things that you may wish to consider.

[Read More]

Thursday May 17, 2012

EPM 11.1.2.2 - Enhance support for LDAP/MSAD connection timeouts

Applies to EPM 11.1.2.2 release.

  • Connection timeout (after inactivity in the system) by Firewall or Load Balancer in front of the LDAP/MSAD servers is handled better by recreating the master context every 15 minutes (as needed basis).
  • Can be tuned from the css.xml file by setting the parameter <masterContextTimeToLive>. Oracle recommends to set this value to slightly lower than the timeout on the Firewall or Load Balancer in front of the LDAP/MSAD servers.

EPM 11.1.2.2 - Performance with IE for 11.1.2.2 release

If you are using Internet Explorer, we strongly recommend you to use IE9 in order to get the best performance with 11.1.2.2. With the 11.1.2.2 release, we now use Oracle ADF (Application Development Framework). IE9 leverages Oracle ADF much better than IE7 or IE8 and will give you the best performance. 


EPM 11.1.2 - How to resolve high memory usage for HFM (Financial Management)

If you use Oracle Database Client 10.2.x or 11.1.x for Financial Management, you must set the StmtCacheSize registry setting for Oracle OLE DB to 10 on all Financial Management application servers and Web servers. This is due to a memory issue in Oracle Provider for OLE DB. The registry setting path is: Hkey_Local_Machine\Software\Oracle\Key_Homename\Oledb. Important Note that the 11.2.x Oracle Database Client should not be changed.

To resolve the high memory usage, enable Statement Caching. The configured value must not be zero. The recommended value is between and 1 and 10.

1. Edit the registry value: Hkey_Local_Machine\Software\Oracle\Key_Homename\Oledb Value Name: StmtCacheSize Value (decimal):1, where Key_Homename refers to the appropriate Oracle Home.

2. Stop and restart the Financial Management application processes.

Reference:http://docs.oracle.com/cd/E17236_01/epm.1112/readme/hfm_1112200_readme.html


About

A blog focused on Tips & Tricks about Oracle Business Intelligence (OBI), Oracle Exalytics and Oracle Enterprise Performance Management (EPM) products.
[Blog Admin: ahmed awan]

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today