Skip to main content

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

NOMSGLOGGINGONDATAERRORLIMIT

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.
Syntax
NOMSGLOGGINGONDATAERRORLIMIT TRUE | FALSE
The default value is FALSE.

DATAERRORLIMIT

Determines the number of records that can be written to an error log during a data load operation.
Syntax
DATAERRORLIMIT n
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

DIMBUILDERRORLIMIT

Determines the number of records that can be written to an error log during a dimension build operation.
Syntax
DIMBUILDERRORLIMIT n
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.
Labels:

Comments

Post a Comment

Popular posts from this blog

PBCS/EPBCS - ASO exclude shared & Dynamic

As you all are aware that Oracle releases patches to EPM cloud every month (EDMCS is released every 2 months) and the patches are applied on first-week of Friday in Dev and third-week of Friday in Prod I did a post long back about a challenge that I have faced in on-premise and how I have addressed that. New functions were released in Nov-2018 release of PBCS. Below is an excerpt from the readiness document. You can find the document here New Aggregate Storage Functions in Calculation Manager The following Aggregate Storage functions have been added to Calculation Manager. These functions filter the shared and dynamic members from the Point of View (POV). The functions can be used in the POV of an Aggregate Storage custom calculation or allocation. @FilterDynamic(Dimension Name, Member Name) removes all dynamic members from the list of members @FilterShared(Dimension Name, Member Name) removes all shared members from the list of members @FilterSharedAndDynamic(Dime...
Post a Comment
Read more

EPM Cloud Tips & Tricks - #1

The first EPM cloud product was released in 2014 and it's been six years till date. I was recently part of an FCCS implementation project. I know what you might be thinking. Coming from completely essbase and planning background and been working on it for almost 12 years and doing an FCCS project? Well, it turned out that way and it was a change for me too than being in my comfort zone and took it as a challenge.  I have been very busy for over the past one year and I didn't really had a chance or time to get back to my blogging and sharing my knowledge. The project finally went live and I am going to share my bit of learnings. Some of it you might alread know The first tip is going to be an easy one and those who have worked in FDMEE / Data Management in the cloud, you might already know it. But, this is very important when it comes to FCCS as zeroes are valid from Balance Sheet standpoint Data Management by default doesn't load zeroes. Below is a excerpt from the document...
1 comment
Read more

EPM Cloud (PBCS/EPBCS/FCCS) - Report Bursting & Reports scheduling

The first product of Oracle EPM cloud was launched in 2014 and it's been 5 years and over the course of these 5 years, Oracle has every EPM product in cloud to what is available in on-premise. With so many products under the EPM belt each with its own functionality, there is a real need to have a single unified reporting tool that can handle all your reporting requirements across all your EPM products at one place. EPRCS (Enterprise Performance Reporting Cloud Service) is the Oracle direction to address all the reporting needs for any organization of any size. If your team is responsible for the management, narrative and external reporting with the ability to author, collaborate and a solid approval process, you definitely have to consider implementing EPRCS at your organization EPRCS can connect to your EPM Cloud products, Essbase cloud and also to your Fusion Applications Essbase app. It addresses all your financial, management, narrative and disclosure reporting. I am not goi...
4 comments
Read more