Explore topic-wise InterviewSolutions in .

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.

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.

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.

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.

It STOPS MEMBER from BECOMING CONSOLIDATE on all DIMENSIONS

It stops member from becoming consolidate on all dimensions

We will RESPOND with YES, because we can have two instances of Essbase with VARIOUS sets of services on the same MACHINE.

We will respond with yes, because we can have two instances of Essbase with various sets of services on the same machine.

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 answer is yes.

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 answer is yes.

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.

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.

We can make it USING INTEGRATION services and the ESSbase STUDIO from the version 11.

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

They have the PURPOSE of COMMUNICATION of the Essbase with the office TOOLS of Microsoft.

They have the purpose of communication of the Essbase with the office tools of Microsoft.

The EXTENSIONS are: .RUL, .CSC and .OTL.

The extensions are: .RUL, .CSC and .OTL.

In Essbase (a database based on files)the DATA storage is MADE in 2GB PAG files that have a sequential way of GROWING.

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

We can’t SHOW UDA’s in the REPORTS so there is no PERFORMANCE CHANGE.

We can’t show UDA’s in the reports so there is no performance change.

The UDA’s don’t have any impact because they don’t MAKE INHERENT CALCULATIONS and the Attribute dimensions the same have no impact because they just make DYNAMIC calculations.

The UDA’s don’t have any impact because they don’t make inherent calculations and the Attribute dimensions the same have no impact because they just make dynamic calculations.

Attribute dimensions are DIFFERENT from UDA’s because of their improved flexibility. The CALCULATION with the attribute CALCULATIONS dimensions with five members named: sum, min, max, count and avg is made automatically and dunamicaly.

Attribute dimensions are different from UDA’s because of their improved flexibility. The calculation with the attribute calculations dimensions with five members named: sum, min, max, count and avg is made automatically and dunamicaly.

Because UDA’s are not NEEDING any SPACE in ADDITION, they don’t have any impact on the size of a DATABASE.

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

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

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

The USER DEFINED attributes are referring to the members classes while the aliases are only different ways to NAME memebres, they are totally separate and have totally separate USAGES.

The user defined attributes are referring to the members classes while the aliases are only different ways to name memebres, they are totally separate and have totally separate usages.

YES, but a DIFFERENT RULE FILE should be used for EVERY dimension.

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

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:

1. Less dimensions and more dense dimensions

The Aggregate Storage Option or ASO:

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

The Block Storage Option or BSO:

1. Less dimensions and more dense dimensions

MaxL SCRIPTS can be CALLED from a BAT file which is USED for SCHEDULING.

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

After a database CRASH or SERVER interruption, Essbase automatically RECOVERS a database after rolling back the transactions that were active at that time.

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

To BACK up an AGGREGATE STORAGE database, copy the application DIRECTORY ARBORPATH/app/appname.

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

Objects gets locked to PREVENT USERS to make simultaneous and conflicting CHANGES to Essbase database objects. By DEFAULT whenever an OBJECT is accessed through Administrative services console or Excel spreadsheet add-in, it gets locked.

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

You should have the ROLE of APPLICATION MANAGER for the SPECIFIED application.

You should have the role of Application manager for the specified application.

When Essbase restructures both the data blocks and the index, it uses the files described

essxxxxx.pag

Essbase data fileessxxxxx.ind

Essbase index filedbname.esm

Essbase kernel file that contains CONTROL information USED for db recoverydbname.tct

Transaction control tabledbname.ind

Free fragment file for data and index free fragmentsdbname.otl

Outline file in which is DEFINED all metadata for a DATABASE and how data is stored

When Essbase restructures both the data blocks and the index, it uses the files described

essxxxxx.pag

Essbase data fileessxxxxx.ind

Essbase index filedbname.esm

Essbase kernel file that contains control information used for db recoverydbname.tct

Transaction control tabledbname.ind

Free fragment file for data and index free fragmentsdbname.otl

Outline file in which is defined all metadata for a database and how data is stored

Intelligent CALCULATION, name changes, and formula changes affect DATABASE RESTRUCTURING:

1. 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.

2. 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.

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

1. 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.

2. 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.

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

The two ways by which a database restructure is triggered:

As your business changes, you change the Essbase database OUTLINE to capture new product lines, PROVIDE information on new scenarios, reflect new time periods, etc. Some changes to a database outline affect the DATA storage ARRANGEMENT, forcing Essbase to restructure the database.

As your business changes, you change the Essbase database outline to capture new product lines, provide information on new scenarios, reflect new time periods, etc. Some changes to a database outline affect the data storage arrangement, forcing Essbase to restructure the database.

You can PREVENT and remove fragmentation:

1. To prevent fragmentation, optimize data loads by sorting load records based upon sparse dimension MEMBERS. For a comprehensive discussion of optimizing data load by grouping sparse members.

2. To remove fragmentation, PERFORM an export of the database, delete all data in the database with CLEARDATA, and RELOAD the export file.

3. To remove fragmentation, force a dense restructure of the database.

You can prevent and remove fragmentation:

1. To prevent fragmentation, optimize data loads by sorting load records based upon sparse dimension members. For a comprehensive discussion of optimizing data load by grouping sparse members.

2. To remove fragmentation, perform an export of the database, delete all data in the database with CLEARDATA, and reload the export file.

3. To remove fragmentation, force a dense restructure of the database.

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.

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.

FRAGMENTATION is likely to occur with the following:

1. Read/write databases that users are constantly updating with data

2. Databases that EXECUTE calculations around the CLOCK

3. Databases that frequently update and recalculate dense members

4. Data loads that are poorly designed

5. Databases that contain a significant number of Dynamic Calc and STORE members

6. Databases that use an isolation level of uncommitted access with commit block set to zero

Fragmentation is likely to occur with the following:

1. Read/write databases that users are constantly updating with data

2. Databases that execute calculations around the clock

3. Databases that frequently update and recalculate dense members

4. Data loads that are poorly designed

5. Databases that contain a significant number of Dynamic Calc and Store members

6. Databases that use an isolation level of uncommitted access with commit block set to zero

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

1. BLOCK Size(8Kb to 100Kb) and Block DENSITY

2. Order of Sparse Dimensions

3. INCREMENTAL Data LOADING

4. Database Outlines with Two or More Flat Dimensions

5. Formulas and Calculation Scripts

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

1. Block Size(8Kb to 100Kb) and Block Density

2. Order of Sparse Dimensions

3. Incremental Data Loading

4. Database Outlines with Two or More Flat Dimensions

5. Formulas and Calculation Scripts

There are several ways to optimize load

1. Grouping of Sparse member combinations

2. Making the DATA source as small as possible

3. Making source fields as small as possible

4. Positioning the data in the same order as the outline

5. Loading from Essbase Server

6. Managing parallel data load processing

There are several ways to optimize load

1. Grouping of Sparse member combinations

2. Making the data source as small as possible

3. Making source fields as small as possible

4. Positioning the data in the same order as the outline

5. Loading from Essbase Server

6. Managing parallel data load processing

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

1. Dimension with ACCOUNTS tag

2. Dimension with Time tag

3. Largest Dense dimension

4. SMALLEST dense dimension

5. Smallest Sparse dimension

6. Largest Sparse dimension

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

1. Dimension with Accounts tag

2. Dimension with Time tag

3. Largest Dense dimension

4. Smallest dense dimension

5. Smallest Sparse dimension

6. Largest Sparse dimension

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)

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)

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.

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.

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.

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.

To COMMUNICATE between ESSBASE and MICROSOFT OFFICE TOOLS.

To communicate between Essbase and Microsoft office tools.

Essbase is an file BASED DATABASE where the DATA is stored in PAG FILES of 2 GB each and grows sequentially.

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

UDA’s VALUES are never DISPLAYED in the reports and hence do not impact REPORT performance.

UDA’s values are never displayed in the reports and hence do not impact report performance.

They are specific objects LIKE files, cell notes or URL’s associated with specific data cells of Essbase database. You can link MULTIPLE objects to a single data cell. These LINKED objects are stored in the server. These LRO’s can be exported or imported with the database for backup and migration activities.

They are specific objects like files, cell notes or URL’s associated with specific data cells of Essbase database. You can link multiple objects to a single data cell. These linked objects are stored in the server. These LRO’s can be exported or imported with the database for backup and migration activities.

The statement should be just opposite. As dynamic calc MEMBERS are calculated when REQUESTED, the retrieval TIME should increase.

The statement should be just opposite. As dynamic calc members are calculated when requested, the retrieval time should increase.

Analytic services (or Essbase Services) locks the BLOCK and all other BLOCKS which contain the Childs of that block while calculating this block is block locking SYSTEM.

Analytic services (or Essbase Services) locks the block and all other blocks which contain the Childs of that block while calculating this block is block locking system.

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.

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.

In the PROCESS it calculates more blocks than is NECESSARY. SOMETIMES it is necessary to PERFORM top-down calculation to get the correct calculation results.

In the process it calculates more blocks than is necessary. Sometimes it is necessary to perform top-down calculation to get the correct calculation results.

LOWER LEVEL members and associated DATA REMAINS in relational database where as upper level members and associated data resides in ESSBASE database.

Lower level members and associated data remains in relational database where as upper level members and associated data resides in Essbase database.

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.

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.

INTEGRATION SERVICES and in VERSION 11, we have Essbase studio.

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

To COMMUNICATE between ESSBASE and MICROSOFT OFFICE TOOLS.

To communicate between Essbase and Microsoft office tools.

No. Because we define ASO or BSO OPTION while CREATING the APPLICATION and not database. Hence if the application is ASO, the databases it contains will be that TYPE only.

No. Because we define ASO or BSO option while creating the application and not database. Hence if the application is ASO, the databases it contains will be that type only.

Yes. But only one DATABASE PER APPLICATION is recommended.

Yes. But only one database per application is recommended.