The first tip is for speeding up data loads to essbase databases and while it may be obvious to many people I often find this setting in the IKM left as default and hear complaints that apparently the essbase adaptor is slow at loading data.
When you first create an interface to load data to an essbase database you will see an option in the IKM called COMMIT_INTERVAL.
As you may be aware there are a couple of methods available to parallel load data into an ASO database, one method is to have multiple sessions of Maxl each performing a data load or the much more efficient way of using one Maxl statement using multiple load rules (up to eight).
The Maxl syntax is
Within EPMA there is built in functionality known as data synchronization which allows the synchronizing of data between EPM products, flat files and interface tables which I will be covering.
Today I am going to look at using ODI to control running of the batch client and add in some error handling functionality. Unfortunately there are no adaptors or API available to use with ODI and EPMA so I am going to use the OS command tool to run the EPMA batch client.
Today I am going to look at automating the process using the EPMA batch client and then move on to using ODI to take over control.
Now you don’t have to use ODI as other methods could be used to populate the tables but I am going to use it as it offers such flexibility around transformations and automation in a controlled environment.
At first there was only Smart View available as a standalone installer, no Excel add-in, Financial Reporting Studio, EAS or Essbase Studio console installers were available.
It wasn’t until a patch release in 188.8.131.52 that the Excel add-in was made available as a standalone installer.