Top 50 Oracle Hyperion Interview Questions You Must Prepare 08.Dec.2023

In Essbase (a database based on files)the data storage is made in 2GB PAG files that have a sequential way of growing.

Yes. But only one database per application is recommended.

Depend on which database that you are going to create. For Example: If you are creating ASO then we can’t create more that 1 db per application. If you are creating BSO then you can create more than 1 db per application

Essbase is an file based database where the data is stored in PAG files of 2 GB each and grows sequentially.

If we have a single processor, we will use serial calculation but if we have multiple processors we can break the task into threads and make them run on different processors.

Yes. We can have multiple instances of an Essbase server on a single machine and there will be different sets of windows services for all these instances.

We have IIS for HFM although there is no IIS for OLAp’s. If there is no IIS then it is a time taking process to recover financial data.

Yes, we can query members for UDA in calculating scripts.

Hyperion is a file that empowers you to access the data quickly. The association was bought by Oracle in 2007 and has continued upgrading the product. The Fancy name of Hyperion is Business Intelligence and its motto is to support better business decision-making.

The clarification behind this is figuring a higher measure of blocks than required and for the right results to show up there is a prerequisite for making a top-down calculation.

Custom defined macros makes use of an internal Ess base macro language that enables to combine calculation functions and also helpful to operate on multiple input parameters.

Yes. We can manage our server resources by starting only the applications which receive heavy user traffic. When an application is started, all associated databases are brought to the memory.

The impact of the Attribute dimensions on the performance of the reports is very high due to the dynamic calculation made referencing the reports. If the number of attribute dimensions shown in the reports is high, this will have a negative impact on performance.

A data block containing cells that have been changed since the last calculation. Upper level blocks are marked as dirty if their child blocks are dirty (that is, have been updated)

To back up an aggregate storage database, copy the application directory ARBORPATH/app/appname.

Oracle Hyperion Financial Management (HFM) is a complete Web-based application that provides global financial alliance, reporting and examination in a single, highly scalable software solution.  Oracle Hyperion Financial Management, part of the Oracle EPM Suite, supports the collection, consolidation and reporting of financial results in multiple GAAPs as well as IFRS, and the reconciliation of differences among the various standards. Hyperion Financial Management can be deployed quickly to integrate data from multiple Oracle and non-Oracle tractional systems, provide top-side reporting that conforms to IFRS requirements, and help organizations make the trition to IFRS.

The two ways by which a database restructure is triggered:

  1. Implicit Restructures
  2. Dense restructure
  3. Sparse restructure
  4. Outline-only restructure
  5. Explicit Restructures

There are several ways to optimize load

@Grouping of Sparse member combinations

@Making the data source as small as possible

@Making source fields as small as possible

@Positioning the data in the same order as the outline

@Loading from Essbase Server

@Managing parallel data load processing

Yes, we can do that but it is recommended to use separate rule file for each dimension

Attribute dim highly impact the report performance as the attributes are calculated vigorously when referenced in the report. For very large number of attribute dim displayed in the report, the performance could extremely decrease. While filling the data, you have applied both the selection and the rejection criteria to a same record. The record will be rejected.

Essbase is an file based database where the data is stored in PAG files of 2 GB each and grows sequentially.

To communicate between Essbase and Microsoft office tools.

We can make it using Integration services and the ESSbase studio from the version 11.

The three primary build methods for building dimensions are:-

  1. Generation references
  2. Parent-Child references
  3. Level references

After a database crash or server interruption, Essbase automatically recovers a database after rolling back the tractions that were active at that time.

We will use the serial calculation only when we have one processor and when we have more than one the operation can be split into threads that will work on the various available processors.

yes, but a different rule file should be used for every dimension.

Intelligent Calculation, name changes, and formula changes affect database restructuring:

@If you use Intelligent Calculation in the database, all restructured blocks are marked as dirty whenever data blocks are restructured. Marking the blocks as dirty forces the next default Intelligent Calculation to be a full calculation.

@If you change a name or a formula, Essbase does not mark the affected blocks as dirty. Therefore, you must use a method other than full calculation to recalculate the member or the database.

There is  a tool given to us by the Hyperion Administrative services  but this only helps with the migration of the application and the objects database while the data is not migrating. In the other two cases the wer is yes.

Yes. But only one database per application is recommended.

It stops member from becoming consolidate on all dimensions

Usually the outline is optimized using the hourglass design for dimension ordering i.e,

@Dimension with Accounts tag

@Dimension with Time tag

@Largest Dense dimension

@Smallest dense dimension

@Smallest Sparse dimension

@Largest Sparse dimension

TB First: The accounts member Opening Inventory in the Sample.Basic database is tagged as TB First. Opening Inventory combines the value of the first month in every quarter and uses that value for that month’s parent.

E.g. the value for Qtr1 is the same as the value for Jan.

TB Last: The accounts member Ending Inventory in the Sample.Basic database is tagged as TB Last. Ending Inventory combines the value for the last month in every quarter and uses that value for that month’s parent.

E.g. the value for Qtr1 is the same as the value for Mar.

To automate the process of creating dimensions with thousands of members.

Integration services and in version 11, we have Essbase studio.

Three types of partitions are there.

@Trparent partition: A form of shared partition that provides the ability to access and manipulate remote data trparently as though it is part of your local database. The remote data is retrieved from the data source each time you request it. Any updates made to the data are written back to the data source and become immediately accessible to both local data target users and trparent data source users

@Replicated Partition

@Linked Partition

It signifies buffer in memory which contains compressed data files (.PAG ).

You can measure fragmentation using the average clustering ratio or average fragmentation Quotient.

Using the average fragmentation quotient

Any quotient above the high end of the range indicates that reducing fragmentation may help performance

Small (up to 200 MB) 60% or higher

Medium (up to 2 GB) 40% or higher

Large (greater than 2 GB) 30% or higher

Using the average clustering ratio:

The average clustering ratio database statistic indicates the fragmentation level of the data (.pag) files. The maximum value, 1, indicates no fragmentation.

Objects gets locked to prevent users to make simultaneous and conflicting changes to Essbase database objects. By default whenever an object is accessed through Aministrative services console or Excel spreadsheet add-in, it gets locked.

Because UDA’s are not needing any space in addition, they don’t have any impact on the size of a database.

Yes, it is. We can begin only those applications that have high traffic, in this way we can save server resources, the memory will be filled with databases at the beginning of the application.

The members with a higher level along with the data associated will stay in the Essbase database while the members of a smaller level and their associated data will live in the relational database.

To communicate between Essbase and Microsoft office tools.

The important LOG files are:

  • Application.log
  • Configtool.log
  • Essbase.log
  • ess base server-install.log
  • eas_install.log

The Essbase Services also known analytic will make a lock to all the blocks that capture the Childs of the initial block, this process is block locking system.

Dense dimension: It is a dimension in which most data exists for every combination of dimension members.

Sparse dimension: It is a dimension which has less probability that data will exist for every combination of dimension members.

Essbase macros that we write with Essbase calculator functions and special macro functions. Custom-defined macros use an internal essbase macro language that enables you to combine calculation function and operate on multiple input parameters.

MaxL scripts can be called from a BAT file which is used for scheduling.

The Aggregate Storage Option or ASO:

  1. Used for more than ten dimensions
  2. The majority of the dimensions will be sparse
  3. It is impossible to write back in ASO.

In the next versions we should be able to write back.

The Block Storage Option or BSO:

@Less dimensions and more dense dimensions

You can configure a database to optimize calculation performance. The best configuration for the site depends on the nature and size of the database.

@Block Size(8Kb to 100Kb) and Block Density

@Order of Sparse Dimensions

@Incremental Data Loading

@Database Outlines with Two or More Flat Dimensions

@Formulas and Calculation Scripts