Fragmentation has a number of potential causes. Identify two.
Answer : B,E
Explanation: Fragmentation is unused disk space. Fragmentation is created when
Essbase writes a data block to a new location on disk and leaves unused space in the former location of the data block. Block size increases because data from a data load or calculation is appended to the blocks; the blocks must therefore be written to the end of a data file."
Fragmentation is likely to occur with the following:
Read/write databases that users are constantly updating with data (E)
Databases that execute calculations around the clock
Databases that frequently update and recalculate dense members (B)
Data loads that are poorly designed
Databases that contain a significant number of Dynamic Calc and Store members
Databases that use an isolation level of uncommitted access with commit block set to zero
You can prevent and remove fragmentation:
To prevent fragmentation, optimize data loads by sorting load records based upon sparse dimension members
Perform an export of the database, delete all data in the database with CLEARDATA, and reload the export file
Force a dense restructure of the database
Reference Improving Essbase Performance, Eliminating Fragmentation
Within which two directories can you set the location and file size in ASO?
Answer : A,D
Explanation: For aggregate storage applications, Tablespace Manager controls data retrieval and storage, using tablespace definitions to manage data storage and work areas on the disk.
Tablespaces help optimize data file and work file storage and retrieval. Tablespaces define location definitions that map data artifacts, such as aggregate views and aggregations, to files. Each application directory contains directories for four tablespaces:
* default
* log
* metadata
* temp
For default and temp you can specify multiple locations and sizes, and you can define tablespace properties:
* Directory path locations
* Maximum disk space to be used at each location
* Maximum file size allowed within each location
Which three statements are true about multiple hierarchies in ASO?
Answer : A,B,E
Explanation: A: The member representing the first hierarchy (top level member of the hierarchy) in a dimension that has multiple hierarchies must be tagged as a stored hierarchy. Analytic Services requires such a hierarchy to be a stored hierarchy.
B: To use multiple hierarchies in a dimension, you must enable multiple hierarchies for that dimension.
E: Alternate hierarchies may be either dynamic or stored.
Reference: 1060180 The primary hierarchy must be tagged as Stored.
Identify the five true statements.
Answer : B,C,E,F,G
Explanation: Differences bettewen CALC DIM and AGG.
CALC DIM (Product);
This line calculates the Product dimension doing both outline aggregation (such as rolling all the Colas up into the parent value) and member formulas (C), if they exist for members in that dimension. If we want to calculate multiple dimensions using this command (say, Market and Product), just separate them with commas:
CALC DIM (Market, Product);
Remember how we said that CALC DIM not only does
aggregation but also member formulas? Well, how many member
formulas are there in the Market and Product dimensions?
Thats right: none, so CALC DIM is wasting time looking for
formulas that you know arent there. For sparse dimensions that dont have formulas, theres a command that only does aggregation and as such, is usually faster:
AGG (Market, Product) (B, F)
Note: The CALC DIM command calculates the formulas and aggregations associated with each member of all the specified dimensions. This command calculates the formulas and aggregations associated with each member of all of the specified dimensions. The order in which dimensions are calculated depends on whether they are dense (G) or sparse (E). All of the dense dimensions are calculated first, in the order that the dense dimensions appear
. The sparse dimensions are then calculated in a similar order.
In an aggregate storage database, which two are the correct member solve orders for Profit per Unit and Variance given the following:
Profit per Unit - Accounts dimension
Variance - Scenario dimension -
When we say "correct," we mean that both dynamic totals will calculate and display correctly.
Answer : C,D
Identify the true statement about the data cache.
Answer : B
Explanation: The Data Cache is a buffer in memory that holds uncompressed data blocks.
Essbase allocates memory to the data cache during data load, calculation, and retrieval operations, as needed.
Note: there are four other caches as well, including the index cache.
What is the extension for the file containing data for ASO applications?
Answer : B
Explanation: For ASO - the data is stored in table spaces in a .dat file in the
\App\Appname\default folder. The format is some type of binary and you cannot open the file and do anything with the contents.
In Smart View, when zooming in and out of dimensions in Essbase, if you need to go back to a previous step, you can:
Answer : A
You need to display a text value based on variance data in an ASO database. If the variance percentage is less than 10, users should see "Low Priority," if the variance percentage is between 11 and 25, users should see "Medium Priority," and if the variance percentage is greater than 25, users should see High Priority." The Essbase feature that supports this capability is:
A. Text List -
B. Format string -
C. Text data type of a measure -
D. Trigger -
E. Not possible in an ASO database
Answer : B To use a format string you just have enable types measures on your outline, then in the -MdxFormat ( string_value_expression )A simple example isMdxFormat(IIF(CellValue() < 0,"Negative","Positive"))
Identify the three true statements about the Administration Services console.
Answer : A,C,D
Explanation: A: Enterprise View can contain multiple Essbase Servers, applications, and databases. You can create custom views of the Enterprise View tree in separate tabs in the navigation pane. Custom views can help reduce the number of mouse clicks it takes to navigate to an object in Enterprise View.
You can add the following Essbase objects to a custom view: Essbase Servers, applications, databases (C), calculation scripts (D), report scripts, filters, and rules files.
You cannot add Essbase users and groups, Essbase Administration Servers (not B), or
Essbase Administration Server users (not E) to a custom view.
You need to track and report the Store Close Date for all of the stores in your company in your block storage option database. Store close date will vary by store over time.
Which three solutions would allow you to do this?
Answer : A,C,E
Identify the three invalid methods to back up ASO database.
Answer : A,C,D
Explanation: A: the MaxL statement alter database begin archive do not support aggregate storage databases.
D: Operating System backup cannot backup the ASO database.
Identify the four true statements about attribute dimensions
Answer : A,D,E,F
Explanation: An attribute dimension is a special type of dimension that is associated with a standard dimensions.
Use attribute dimensions to report and aggregate data based on characteristics of standard dimensions.
Essbase does not allocate storage for attribute dimension member (not C). Instead, it dynamically calculates the members when the user requests data associated with them
(D).
Attribute dimensions are always sparse dimensions(not B). And you can associate attribute dimensions only with sparse standard dimensions
A, D, F:
You notice that your reports are running slower than before and realized that nothing in terms of data volume or dimension members has changed. You also checked the log file and found that no one ran any calculation.
Which two would you look for to diagnose the cause of this slower response time?
Answer : A,C
Explanation: A: Database fragmentation would slow down the database performance. You can use MaxL commands to check the fragmentation status.
C: The data cache could affect the running time of the reports. Checking this cache would be a good idea.
Incorrect answers -
Stop time of the application is not of interest here.
The commit-level setting would affect real-time updates, not producing reports.
You have a reporting requirement to track and report the employee status for employees in your workforce ASO Essbase database. Employee status can change over time. One report requires employees down the rows and employee status across the columns.
What is the best solution to meet the all of the requirements?
Answer : D
Explanation: D: An attribute dimension is a special type of dimension that is associated with a standard dimensions.
Use attribute dimensions to report and aggregate data based on characteristics of standard dimensions. In the Sample.Basic database, for example, the Product dimension is associated with the Ounces attribute dimension. Members of the Ounces attribute dimension categorize products based on their size in ounces.
Essbase does not allocate storage for attribute dimension member. Instead, it dynamically calculates the members when the user requests data associated with them.
Attribute dimensions are always sparse dimensions. And you can associate attribute dimensions only with sparse standard dimensions