Wednesday Apr 23, 2014

Error Connecting to Planning Application from Smartview

When the OU of a user is changed in the external provider, users can potentially have issues connecting to Planning applications from Smartview. However, users can still log into Planning just not Smartview. [Read More]

Wednesday Jan 22, 2014

Essbase 11.1.2.x - Web Launched EAS Console jnlp

When using the web launched EAS Console with internet explorer (http://<servername>:10080/easconsole/console.html) for the first time , it is possible that you will be prompted to open, find or save the easconsole.jnlp.


[Read More]

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]

Wednesday Sep 04, 2013

Essbase 11.1.2.x - Changing Essbase ODL Logging Levels

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.

[Read More]

Tuesday Jul 30, 2013

Disabling Implied Share for an Essbase Application

Implied share is the default behavior in Essbase where a data relationship is shared explicitly between parent and child members in the outline. Implied share occurs when a parent has a single child or a parent has only one child of many children that consolidates to the parent in an Essbase outline.

If you need to disable all implied shares in a given outline, there is an Essbase configuration setting that can be set in the Essbase.cfg file. As part of the supported steps, it is recommended to rebuild the outline after the IMPLIED_SHARE <ApplicationName> FALSE setting is in place. This post it to help the field where in certain situations rebuilding the outline may be challenging. There is a way to set an existing outline to have implied share disabled, however, there are risks associated with these steps and no guarantee the metadata and data implied share setting are in sync. If there are any issues after following the “unsupported” steps, Oracle Support will require that the supported steps be followed first.

[Read More]

Saturday Jul 20, 2013

Performance issues after upgrading Essbase outlines from 11.1.1.x to 11.1.2.x

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

EPM 11.1.2.2: How-to Setup Essbase Clustering on Unix

The steps on how to setup Essbase clustering on the 11.1.2.2 release has changed as compared to the previous releases.  This document goes through how to setup Essbase clustering on Unix on the EPM 11.1.2.2 release.  The information provided in this document has been taken from the EPM 11.1.2.2 Installation and Configuration Guide, which can be found here @ http://docs.oracle.com/cd/E17236_01/epm.1112/epm_install_1112200.pdf

> Download the Essbase clustering on the 11.1.2.2 release step by step document

 


 

Wednesday Apr 24, 2013

Essbase Aggregate Storage (ASO) - Incremental Outline Updates Triggers a Full or Light Outline Restructure

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.


[Read More]

Friday Jan 25, 2013

Merge Data Slices Before Copying an Aggregate Storage (ASO) Application

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 11.1.2.2.100 readme documentation. See the current Essbase 11.1.2.2.100 readme documentation under Documentation Updates: http://docs.oracle.com/cd/E17236_01/epm.1112/esb_11122100_readme.pdf

Wednesday Dec 19, 2012

EPM 11.1.2.2 Architecture: Essbase

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]

Wednesday Dec 12, 2012

EPM 11.1.2.2 Architecture: Financial Performance Management Applications

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.

[Read More]

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]

Friday Nov 30, 2012

Using Transaction Logging to Recover Post-Archived Essbase data

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

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]
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
24
25
26
27
28
29
30
   
       
Today