Oracle Updated 1z0-591 Exam Questions and Answers by marco

Oracle Essbase developers creating planning and budgeting applications have been keenly aware of the advantages and disadvantages of the two different storage types available to them:

* Block storage option (BSO) databases support a wide range of calculations, including forecasts, allocations, and aggregations through procedural calculation scripts. The results of these calculations can be written back to the database, but applications that use BSO storage are limited to about 10 dimensions and member counts in the low hundreds of thousands.

* Aggregate storage option (ASO) databases can support about 20 dimensions and member counts in the millions. ASO databases use multidimensional functions rather than procedural scripts to perform calculations, but the results of queries cannot be stored back in the database, making ASO unsuitable for most financial management applications.

Level-based Hierarchy

Level-based hierarchy is the first type of hierarchy in OBIEE.

Consists of an ordered set of two or more levels. For example, a Time hierarchy might have three levels for Year, Quarter, and Month. Level-based hierarchies can also contain parent-child relationships.

Dimension hierarchy levels allow :

* to perform aggregate navigation,

* to configure level-based measure calculations,

* users from Dashboard and Answers to drill down from one parent to a child level.

Special type of level-based dimension are supported:

* Unbalanced (or ragged) and Skip-level hierarchy

* time dimension to provides special functionality for modeling time series data.

In a standard OBIEE implementation, we generally want to purge and re-build the cache after every ETL (extract, transform, and load) run.