Finding the Dirt: tricks for rapid Prototyping with Essbase Studio - Developing Essbase Applications - page 99

Figure 3.33 Defining hierarchy as Dynamic.

you can turn off duplicates on a level-by-level basis in that dimension and continue to
validate the outline until you focus in on the specific members that are causing the issue.
Along the same line, when you are dealing with ASo models, you can set the dimension
types to all “Dynamic” for initial deployment purposes, as in Figure 3.33.
Even after you have scrubbed duplicate members out of the dataset, you might end
up in a situation where multiple shared members appear in a dimension hierarchy. Like
unexpected duplicates, this causes the cube deployment to fail on the Essbase side.
making all dimensions dynamic on the initial deployment, Essbase allows all consoli-
dation operators and multiple shared members to deploy in a dimension or hierarchy. In
a similar process to duplicate, you can then go into EAS and toggle each dimension from
“dynamic” to “stored” or to “multiple hierarchies enabled” and validate the outline. This
lets you see the specific hierarchies and members where you have issues.

3.6.3 Incremental Building to Validate Dimensionality
one final consideration in deploying the cube from Studio is leveraging incremental
build options. This makes sense, of course, when adding to an existing cube. It also is
quite useful when first deploying a cube.
The deployment process from Studio can take minutes or hours (usually somewhere
in between). At any point during the deployment, if a dimension fails the entire deploy-
ment is aborted (even if multiple other dimensions have, in theory, built correctly).
If you are dealing with large dimensions, such as a “Work order tasks” dimension with
a million members, a failure can cost you hours of downtime. Instead, you can leverage
the incremental build capabilities to deploy the model one dimension at a time and key
in on a dimension or set of dimensions that cause a failure.
to leverage incremental building on the initial deployment:

1. Create an empty application and database in using Essbase Administration
Services.

2. In Studio, initiate the Cube Deployment Wizard.

3. Fill in the Application and Database name with the application and database
you created in step 1, and click Next .

4. Select the option for Incremental Load (Figure 3.34).

5. In the Scheduling options area, select Deploy Now and click Next .

6. Select Update or Build Selected Hierarchies (Figure 3.35).

7. Select a desired hierarchy or hierarchies and click Rebuild .