Ensurepass.com : Ensure you pass the IT Exams 2018 Jan Oracle Official New Released 1z0-531
100% Free Download! 100% Pass Guaranteed!
Oracle Essbase 11 Essentials
Question No: 21
You need to tune a block storage option database for calculations on a 32bit Essbase server. Identify the two starting point tuning steps that you might take (assuming no direct I/O).
Set Index Cache the size of the index file
Set Data Cache to the size of 0.125 * pag file
Set Data File Cache to the size of .025 * data file
Reset sparse and dense dimensions to achieve a block size greater than 100KB
Explanation: Here are the best practices to tune a BSO database:
ACR (Average clustering Rate) should be as close to 1 as possible, launch a dense restructure to de-fragment the database
Block Size should be between 10 and 100KB (can be more on 64 bit systems)
Data cache should be 12.5% of the pag files (B)
Index cache should be the same size as the ind files (A)
1 Database per Application
Question No: 22
The following two members would be optimally tagged Label Only.
Explanation: Label only is a tag that you can apply to a member to indicate that :
you don#39;t want to store data.
the Members do not have data associated with them.
Use Label Only for member like Scenarios, Ratios, or Drivers, members whose sole purpose in life is to organize the dimension and hierarchy.
Although a label only member has no data associated with it, it can display a value. The label only tag groups members and eases navigation and reporting. Typically, label only members are not calculated.
For example, in the Measures dimension, the member Ratios has three children, Margin%, Profit%, and Profit per Ounce. The member Ratios defines a category of members. When consolidated, Margin%, Profit%, and Profit per Ounce do not roll up to a meaningful figure for Ratios. Hence, Ratios is tagged as label only.
Question No: 23
Your current block storage option design includes two dimensions: Markets and Regions. The Market dimension looks like:
Users need to be able to report by both regions and markets. Subtotals for Northeast and Southwest will display on some reports.
Add another level to the market dimension for Northeast with North and East as children and Southwest with West and South as children
Add an alternate hierarchy to the market dimension with the states as shared members, rolling up to Northeast and Southwest
Create a UDA with members Northeast and Southwest (associated to states in the Market dimension)
Create an attribute dimension with members Northeast and Southwest (associated to states in the Market dimension)
Create a Text list with the values containing the members Northeast and Southwest.
Explanation: Essbase supports this concept called UDA’s wherein one can assign the same attribute to multiple dimension members so that one can do cross dimensional attribute analysis. For example, if you take the default Sample-gt; Basic database you would notice that the Market Dimension members would have some UDA’s assigned to it like Major Market, Small Market etc.
Note: user-defined attributes (UDAs).
Question No: 24
Given the following, what is the block size In bytes?
Block size = 40 * 17 * 2
Block size = 40 *17 * 2 * 8
Block size = 50 * 17 * 5
Block size = 50* 17*5 * 8
Explanation: We need to multiple the stored (not the total) members of the dense dimensions (here Measures: 40, Time:17, and Dense:2) with 8 to calculate the block size.
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: 25
Which two statements are true (assuming data is loaded to a BSO database and to the members noted below)?
If you delete a sparse shared member, the outline file shrinks.
If you delete a sparse shared member, the page file shrinks.
If you delete a sparse stored member, the index file shrinks.
If you delete a sparse stored member, the block density shrinks.
If you delete a dense shared member, the block size shrinks.
If you delete a dense stored member, the number of blocks shrinks
Explanation: C: If a member of a sparse dimension is moved, deleted, or added, Essbase restructures the index and creates new index files. Restructuring the index is relatively fast; the time required depends on the index size.
Sparse restructures are typically fast, but depend on the size of the index file(s). Sparse restructures are faster than dense restructures.
Question No: 26
Which four are the directories used for aggregate storage databases?
Explanation: ASO (Aggregate storage option):
Directory structure differs in both content and purpose from BSO
Tablespaces are utilized to store data and metadata
** Default – stores numeric data (.dat file)
** Log – records database activity
** Metadata – stores metadata information about the objects in the database
** Temp – temporary working space for the Essbase kernel
Question No: 27
What is the default calculation order for ASO database?
Accounts, Time, all remaining dimensions in ascending order of member count
Time, Accounts, all remaining dimensions in ascending order of member count
Accounts, Time, all remaining dimensions in descending order of member count
Time, Accounts, all remaining dimensions in descending order of member count
Dynamic hierarchies, Stored hierarchies
Stored hierarchies, Dynamic hierarchies
Explanation: Aggregate storage calculation order and block storage calculation order differ. For aggregate storage databases, Essbase calculates data in the following order:1.Aggregates members of stored hierarchies and attribute dimensions. The order in which members and dimensions are aggregated is optimized internally and changes according to the nature of the database outline and the existing aggregations…2.Calculates dynamic hierarchy dimension members and formulas…
Note: BSO calculations order: First, Accounts
Third, remaining dense dimensions Fourth, remaining sparse dimensions Two Pass Calculation
Question No: 28
You are creating a MaxL script to log into the database, update a dimension, load data, and run a calculation. Identify the two true statements about creating this MaxL script.
A separate MaxL script is required for each step
The password must be hardcoded into the script when logging in.
IFERROR can be used in MaxL to handle errors after each statement, when triggered will skip to a subsequent statement
Variables for objects like server names, application names and database names can be used in a MaxL script to help with maintenance
Explanation: C: iferror instructs the MaxL Shell to respond to an error in the previous statement by skipping subsequent statements, up to a certain location in the script that is defined by a label name.
Goto forces the MaxL Shell to branch to a certain location in the script defined by a label name; goto is not dependent on the occurence of an error.
Syntaxiferror LABELNAMEgoto LABELNAMEdefine label LABELNAME
D: In the MaxL Shell, you can use variables as placeholders for any data that is subject to change or that you refer to often; for example, the name of a computer, user names, and passwords. You can use variables in MaxL scripts as well as during interactive use of the shell. Using variables in MaxL scripts eliminates the need to create many customized scripts for each user, database, or host.
Variables can be environment variables (for example, $ARBORPATH, which references the directory Essbase is installed to), positional parameters (for example, $1, $2, etc.), or locally defined shell variables.
All variables must begin with a $ (dollar sign). Locally defined shell variables should be set
without the dollar sign, but should be referenced with the dollar sign. Example: set A = val_1;
echo $A; val_1
A MaxL cannot contain several steps. Example:
login $1 $2;
import database sample.basic dimensions from data_file #39;C:\\data\\dimensions.txt#39; using rules_file #39;C:\\\\data\\rulesfile.rul#39;
on error append to #39;C:\\\\logs\\dimbuild.log#39;; iferror #39;dimbuildFailed#39;;
import database sample.basic data from data_file quot;$ARBORPATH\\app\\sample\\basic\\calcdat.txtquot; on error abort;
define label #39;dimbuildFailed#39;; exit;
B: It is recommend that you encrypt the MaxL scripts that includes user names and password, but it is not required.
MAXL is an script language that we could use to manipulate essbase, we could use it to