Database Reference
In-Depth Information
Scripts folder. right-click on the report Script you want to keep and copy it to the new
ASo cube. After repeating this for each report Script, open each one in the ASo cube
and validate the script for potential syntax errors that may arise due to changes in the
outline during the conversion process.
Note: If you have report Scripts that are used as part of the validation process, these are
great to run after you load the same data in both the BSo and ASo cubes for compara-
tive purposes. This will test the script conversion as well as testing the cube conversion
by evaluating whether the results in both executed scripts match.
Calculation Scripts are the last object that you will need to spend time considering
how to handle in the conversion process. This is not as simple as converting the rules
files or report Scripts. remember that a careful review and assessment of the Calculation
Scripts should have been performed prior to starting the conversion process to determine
whether the BSo cube was an appropriate candidate to be converted to an ASo cube.
When discussing Calculation Scripts, there are several things that need to be clarified
right away or you will risk becoming very confused in an extremely short matter of time.
As you know, BSo Calculation Scripts have a .csc extension in the file system and
are most commonly stored in the database directory of an Essbase application. In the
11.1.2.x release, Custom Calculations on Aggregate Storage Databases were introduced.
This has commonly been referred to in blogs and other media as Calculation Scripts for
ASo cubes. In many respects, this is a true statement. These are still in their infancy and
they are certainly not as robust as a BSo Calculation Script. They are a start, a beginning
point that oracle will continue to build upon. The DBAg reveals the fact that Custom
Calculations were created to “extend the analytic capabilities of Essbase by enabling the
execution of recurring calculations on aggregate storage databases.” These calculations
can only target Level-0 cells and they are written using mDx. once the file is created,
these objects also have the .csc extension. In case you are curious, this .csc object cannot
be run like a calculation script in a BSo cube. They can only be executed in one of three
ways (none of which is a right-click in EAS):
•  using the aggregate storage version of the maxL execute calculation statement
•  using the Essbase Application Programming Interface (API)
•  using hyperion Calculation manager to design and deploy to Enterprise
Scheduling Services
See the “Sample use Case for Custom Calculations” in the DBAg for more detailed
information. hence, while the object extension is familiar and the concept is familiar,
Custom Calculations are not like anything you may have previously used. As they exist
today, these will take some study and consideration to determine best use cases for them
in ASo cubes.
A third object with a .csc extension in Essbase is a stored aggregation file. Later in
this chapter we will discuss the process of saving of recommended aggregate views.
The file created by this process has a .csc extension and it also is located in the database
directory (the same location as the Calculation Script in a BSo cube). Three different
objects with the same extension could be confusing if you do not understand ahead of
time what you are creating.
given these facts, what do you do with Calculation Scripts in an ASo conversion?
typically, you would evaluate the contents of the Calculation Script and determine how
you will handle the existing process the script provides given the capability of the ASo
Search WWH ::




Custom Search