Oracle Essbase 11 Essentials
Question No: 31
Which setting will give information about when a data block is calculated?
SET MSG INFO;
SET MSG SUMMARY;
SET MSG DETAIL;
SET MSG WARNING;
Explanation: The command SET MSG sets the level of messaging you want returned about calculations, and enables simulated calculations.
SET MSG SUMMARY | DETAIL | ERROR | WARNS | INFO | NONE | ONLY;
SET MSG DETAIL provides the same information as SUMMARY. In addition, it displays a detailed information message every time Analytic Services calculates a data block.
Question No: 32
What are the three rules for Shared Members in ASO?
A Multiple Hierarchy Enabled dimension can have shared members.
When a hierarchy is tagged Multiple Hierarchies Enabled, it must be store.
The alternate hierarchy has shared members that refer to nonshared members of previous hierarchies in the outline.
The shared members roll up according to a different hierarchy from the nonshared members to which they refer.
Explanation: Shared member hierarchy is also an alternate hierarchy. All shared member refers to stored members of outline (C). In aggregate storage application only multiple hierarchies can have shared members. (A)
Stored hierarchy has only addition as consolidation operator. You can use the stored hierarchy type where aggregation is the only mathematical requirement. If you have some shared member in hierarchy then use multiple hierarchy.
Question No: 33
Changing a dense dimension member from stored to dynamic causes .
a Full restructure
an Index restructure
an Outline restructure
Explanation: These types of restructure operations are listed from fastest to slowest:
Outline only (no index or data files)
Sparse (only index files)
Dense (index files and data files) as a result of adding, deleting, or moving members and other operations.
Dense (index and data files) as a result of changing a dense dimension to sparse or changing a sparse dimension to dense (A)
Question No: 34
Which two valid field headers could be assigned to the 5th column in this data file? Duplicate Member Names is not enabled.
Explanation: A: Regarding Table Aliases: You can assign one or more alternate names, or aliases, to Planning Account, Currency, Entity, Scenario, Period, Version, Year, and user- defined dimension members. Aliases provide the ability to create unique sets of identifiers when working with dimensions and members.
Planning allows up to 10 aliases per dimension member, including the default alias.
C: The terms quot;generationquot; and quot;levelquot; denote the distance from either the quot;rootquot; or the quot;leavesquot; of the dimension. Thus, you can determine the location of any member within a database tree. You can also specify relationships between groups of related members. Generations specify the distance of members from the root of their dimension. All members in a database that are the same number of branches from their root have the same generation number. The dimension is generation 1, its children are generation 2, and so on.
Levels measure the number of branches between a member and the lowest member below it, that is, the number of branches between a member and the quot;leafquot; of its hierarchy within the database structure. Level 0 specifies the bottom-most members of a dimension and thus provides ready access to the raw data stored in a database. Leaf members are level 0, then their parents are level 1, and so on up the hierarchy.
You might note that when all sibling members have the same generation number but not necessarily the same level number.
For example, the members in this hierarchy:
m12 m121 m122
have the following generation and level numbers:
Dim1 Gen 1, Level 2
m11 Gen 2, Level 1
m111 Gen 3, Level 0
m112 Gen 3, Level 0
m12 Gen 2, Level 1
m121 Gen 3, Level 0
m122 Gen 3, Level 0
m13 Gen 2, Level 0
B: Attributes let you add another level of granularity to your data. You create attributes for a
dimension when you want to group its members according to the same criterion. You then create attribute values for each attribute, which are assigned to dimension members.
D: You can use user-defined attributes (UDAs)-words or phrases describing a particular characteristic of members-within calc scripts, member formulas, and reports so that they return lists of members associated with the specified UDA. For example, say you have a Product dimension with various product members. s. You could create a UDA called New Products and base certain calculations only on new products.
Question No: 35
Which files will get restructured in a full BSO restructure?
Data file only
Index file only
Data and index file
Explanation: There are two types of restructures of Essbase BSO databases. Full/dense restructure recreates the index file (Ess*.IND) and the data file (Ess*.PAG). A sparse restructure recreates the index file (Ess*.IND) only.
Question No: 36
What are five reasons to use Attributes over a Shared Members dimension?
To create crosstab reports
To describe a dense dimension
To describe a sparse dimension
To perform comparisons based on certain type of data
To perform calculations based on characteristics
To add dimensionality to the database without increasing database size
Explanation: C: Attribute dimensions can only be applied to sparse dimensions.
F: Varying attributes let you vary information in one dimension by up to four additional dimensions.
A, D, E:
B: Attribute dimensions can only be applied to sparse dimensions.
Question No: 37
What is the correct variance formula for an ASO database that recognizes Expense and Non-expense accounts?
[Actual] – [Budget]
[Budget] -[ Actual]
IIF (IsUda([Measures.currentmember], quot;Expensequot;), [Budget]-[Actual], [Actual]-[Budget])
Explanation: The following MDX formula is appropriate here:
IIF ( IsUDA ([Measures].CurrentMember, quot;Expensequot;),([Budget] – [Actuals]),([Actuals] – [Budget]))
Note #1: Member formula conversions for variance calculations can be accomplished with the help of User Defined Attributes (UDAs) that flag expense items.
A combination of UDAs and conditional logic in ASO outlines provides the equivalent of the Expense Reporting functionality available in BSO outlines.
Note #2: Note: The MultiDimensional eXpressions (MDX) language provides a specialized syntax for querying and manipulating the multidimensional data stored in OLAP cubes.
While it is possible to translate some of these into traditional SQL, it would frequently require the synthesis of clumsy SQL expressions even for very simple MDX expressions. MDX has been embraced by a wide majority of OLAP vendors and has become the standard for OLAP systems.
Reference: Converting a Block Storage Outline to Aggregate Storage in Essbase, Calculating Scenario Variances Using Conditional Logic
Question No: 38
Given the following, what is the declared block size?
Explanation: We need to multiple the stored (not the total) members of the dense dimensions (here Year: 12, Measures:20, and Scenario:2) with 8 to calculate the block size.
Block size: 12x20x2x8 = 3840
Note: Data block size is determined by the amount of data in particular combination of dense dimensions. For ex: when you change the dense or sparse configuration of one or more dimensions in the database, the data block size changes. Data block size is 8n bytes, where n is the number of cells that exist (ie. Stored, not total) for that combination of dense dimensions.Note: Optimal range is 8 to 100 kb
Question No: 39
You receive the following error: Error: 1042018: Network error: The client or server timed out waiting to receive data. Which two settings in the Essbase.CFG are most commonly used to correct the issue?
Explanation: 1042018 Network error: Reference: 1042018 Network error
The server computer or client computer cannot receive data using a TCP/IP network connection.
Check network connections.
Increase the values for NETDELAY and NETRETRYCOUNT.
Question No: 40
Which statement related to Essbase design is true?
Calc scripts are more efficient at performing calculations vs. member unary operators and member formulas
One big application is better than three smaller focused applications.
Attribute dimensions require less performance consideration in ASO databases because they are treated as alternate rollups
Attribute dimensions require less performance consideration in BSO databases because they are dynamically calculated
Bigger block sizes are better than smaller block sizes