Social Icons

Monday, July 21, 2014

Hyperion Performance Scorecard - Statement Of Direction

Oracle Product Management have released the Statement of Direction for Hyperion Performance Scorecard (HPS). This document is available to download from My Oracle Support (MOS) Knowledge Article:

Hyperion Performance Scorecard Statement of Direction -  Doc ID 1901891.1

11.1.2 is the final release version for Hyperion Performance Scorecard. If you have "Hyperion Performance Scorecard" implemented at your place, You might have to go through the document for the Oracle strategy

From the document, It is evident that Oracle future's direction is towards "Oracle Scorecard and Strategy Management" which has a very tight integration with OBIEE
Below is an excert from the SOD regarding the support policies

Note: You need to have a support ID to login to the support portal to access the document.

Monday, July 14, 2014

Essbase Data load & Dimension Build Error log limit

If you are working on a project or in support, there are changes when you do not have the metadata in the system and you try to load data and you get lot of data rejects. 
     You then try to rebuild those members and then try to load the error file again and you get some more rejects. You might be wondering why not all the errors gets updated to the log file? Is there any limit to the number of errors that are written to the file?

Yes. There is a limit both for DataLoad & DimBuild which can be defined in essbase.cfg file and the limit is different for "Dimension Build" and "Data Load"

If you have checked the Technical Reference, you will see three configuration settings

Taken from Dbag


Prevents data load or dimension build errors from being written to the application log after the limit described by the value of DATAERRORLIMIT is reached.
The default value is FALSE.


Determines the number of records that can be written to an error log during a data load operation.
Where n is the number of records, per data load or dimension build, that can be written to the error log, dataload.err. Default: 1000. Maximum: 65,000.
Errors would still be updated to the log file unless you set the NOMSGLOGGINGONDATAERRORLIMIT


Determines the number of records that can be written to an error log during a dimension build operation.
Where n is the number of records, per dimension build, that can be written to the error log, dimbuild.err. Default: 20,000. Maximum: 65,000.

You have to restart your essbase services as the configuration settings will get affected only after the services restarted

Hope this information helps and reduce the number of iterations that you do while loading the data to find out that you still have error records showing up

One ideal solution is to list down the unique number of members and do an adhoc retrieve and see how many members are there in the system and how many new members have come up.