Documente Academic
Documente Profesional
Documente Cultură
names of members.
By default, Essbase creates a symmetric report unless you select
the same number of members for all column dimensions.
}=>. What is the maximum number of parallel threads used to
calculate?
Ans: Four threads.
}=>. How does Report Extractor Retrieves Data?
The Report Extractor processes the report script and retrieves data
in the following Order:
Composes the member list, based on all possible member
combinations.
For example, the following command retrieves member East and all
of its Descendants:
}=> IDESCENDANTS East
}=> Applies member restrictions. For example, the following
command refines the member selection: LINK
}=> Orders the member output. For example, the following
command determines the order in which members are sorted:
SORT
}=> Extracts data from the following areas:
Local regions
Partitioned regions
Dynamically calculated data
}=> Restricts data. For example, the following command suppresses
the display of all rows that contain only missing values:
{SUPMISSINGROWS}
}=> Sorts data. For example, the following command returns rows
with the highest Values of a specified data column: TOP
}=> Formats output. For example, the following command skips one
or more lines in the final output report: {SKIP}
The order in which the Report Extractor retrieves data is important
when using complex extraction and formatting commands. For
example, because the Extractor restricts data (step 5) before sorting
data (step 6), if you place conditional retrieval Commands in the
wrong order, the report output results could be unexpected. Be
aware of the data retrieval process when designing your report
scripts.
}=>. What is a batch POV (Point of View)?
Ans: The batch POV is a collection of all dimensions on the user
POV of every report And book in the batch. While scheduling the
batch the members selected on the batch POVs may be set.
}=>. Point of View (POV)?
Ans: A Unique set of dimension members that define specific
intersection of data.
}=>. Extensible Markup Language (XML)?
Ans: A Language comprised of set of tags used to assign attributes
to data that can be interpreted between the applications based on
the schema used.
}=>. What is a Grid POV?
Ans: The Grid POV enables designers to specify the members for a
dimension on a grid with out placing the dimension on the row,
column or page intersection. The report designer can set the POV
Values at the grid level, preventing the user POV from affecting the
particular grid. If a dimension has only one value for the entire grid,
the dimensions should be put in to the grid POV instead of the row,
column or page.
}=>. Why do you need a batch POV?
Ans: It allows anyone scheduling the batch to use the same default
values for all the grids in all reports in the batch simultaneously
when the batch is run. It is specific to a data source for a single
batch, but not specific to any report or grid to a report in a batch.
Since the batch POV values are only saved when the batch is
scheduled, you can set different values for the same batch.
Changes to the batch POV do not effect the designers POV the
changes to the designers POV do not effect the users POV.
}=>. What are Report member selections?
Ans: The Report member selections define the values for the values
for any dimensions not in the grids row, column, or page axis or set
in the grid POV for all reports in a specific report in the book.
}=>. Why do you need a book POV?
Ans: It allows anyone running the batch to use the same default
values for all the grids in all reports in the book simultaneously each
time the book is run. It is specific to a data source for a single book,
but not specific to any report or grid object in a report in that book.
As the book POV values are saved with the book itself, changes to
the book POV does not affect the designers POV.
}=>. Explain what the Never Share property is?
Ans: Never share: this property is tagged to any of the sparse
member such that it doesnt share the data with its parent/children
even though there is an explicit relationship exits but the data is just
duplicated.
}=>. What are the different types of reports you can produce using
report scripts?
Ans: Sym, asym.
}=>. In how many ways can you get a data out of Essbase cube?
Ans: Using Report script, with export command or function and
Excel spread sheet add-in.
}=>. What does a Label only do? When you retrieve a Label Only
tagged member in a report which has three children what value
would you see?
Ans: It just carries the first childs value Label only tag will be used
so that the data is not consolidated to the higher level or generation
member or to the parent and we dont see any value if we retrieve a
label only tagged member.
}=>. Why do you use a load rule?
Ans: Load rule is used to create or update outline and/or load the
data in the outline.
}=>. How do you clear a specific block in the cube?
Ans: CLEARBLOCK OR CLEARDATA with or without using FIX
command. FIX (Actual)CLEARBLOCK NONINPUT; ENDFIX
}=>. What is the limit on the name of app and database?
Ans: App: 8 bites and database: 8 bites
}=>. How do you zoom only to the next level in the report?
Ans: we need to go to view menu and click on the zoom in to the
next level
}=>. What is the max length of filter we can write in Essbase }=>5
and lower version?
Ans: 64kb
}=>. Which one of the following is fixed? Data file size, Data cache
size, Page files size, index file size.
Ans: Index file 8kb.
}=>. What is committed and Uncommitted Access?
Ans: Committed access provides a high level of data consistency
because only one transaction at a time is written to data block.
Under committed access, Essbase allows transactions to hold
read/write locks on all data blocks involved with the transaction until
the transaction completes and commits. However, you can still allow
read-only access to the last committed data values. It is time
consuming if the data size is too large. Uncommitted access
(enabled by default), the Essbase kernel allows transactions to hold
read/write locks on a block-by-block basis; Essbase releases a
block after it is updated but does not commit blocks until the
transaction completes or until a specified limit (a synchronization
point) has been reached. You can set this limit, as described below.
It is faster, but in case of catastrophic conditions loads data
again.Concurrent users accessing the same data blocks might
experience unexpected results under uncommitted access, because
Essbase allows read-only access to data at its last commit
point.With uncommitted access, you can control when Essbase
performs an explicit commit operation by specifying synchronization
point parameters: Commit Blocks (number of blocks modified before
a synchronization point occurs). The default is 3,000.