1z0-591 Oracle Business Intelligence Foundation Suite 11g Essentials Free Practice Exam Questions (2025 Updated)

The rank measure is numbered from 1. The highest sales amount will be ranked 1.

Steps for Creating Aggregate Tables in OBIEE

1. Create all Dimension Tables, Fact Tables & Hierarchies, which are required to be aggregated.

2. Go to ToolsàUtilities (from Administration tool menu bar), a dialog box will pop up with all available utilities.

3. Select Aggregate Persistence Wizard, and then click Execute Button.

4. Now Select appropriate path where you need to generate Aggregate Table SQL.

Note : Click Generate DDL file for first time generation of Aggregate Table

Click Next, to move to next page (Select Business Model & Measure Page)

In Select Business Model & Measure Page, Select Appropriate Business Model & then select associated Fact / Measure.

Etc.

Steps to Create a Dimension Hierarchy - >Create a dimension object.Add a parent-level object.Add child-level objects.Determine number of elements.Specify level columns.Create level keys.Create a level-based measure.Create additional level-based measures.Create share measures.Create rank measures.Add measures to Presentation layer.Test share and rank measures.

Web Catalog does contain object permissions: folder, reports, etc. The repository has objects permissions to Subject Areas, etc.

Oracle Essbase developers creating planning and budgeting applications have been keenly aware of the advantages and disadvantages of the two different storage types available to them:

* Block storage option (BSO) databases support a wide range of calculations, including forecasts, allocations, and aggregations through procedural calculation scripts. The results of these calculations can be written back to the database, but applications that use BSO storage are limited to about 10 dimensions and member counts in the low hundreds of thousands.

* Aggregate storage option (ASO) databases can support about 20 dimensions and member counts in the millions. ASO databases use multidimensional functions rather than procedural scripts to perform calculations, but the results of queries cannot be stored back in the database, making ASO unsuitable for most financial management applications.

Dynamic Repository Variables:

You initialize dynamic repository variables in the same way as static variables, but the values are refreshed by data returned from queries. When defining a dynamic repository variable, you will create an initialization block or use a pre-existing one that contains a SQL query. You will also set up a schedule that the Oracle BI Server will follow to execute the query and periodically refresh the value of the variable.

Note: The value of a static repository value is initialized in the Variable dialog box. This value persists, and does not change until an Oracle BI Administrator decides to change it.

It is asking for Which task (NOT Which Tasks).

Using Administration (not Administrator) link in OBIEE you can go to 'Manage Map Data' and manage map components.

All others are names for level-based measure but Sales is a base measure.

The value of a static repository value is initialized in the Variable dialog box. This value persists, and does not change until an Oracle BI Administrator decides to change it.

The Oracle BI repository development process adheres to the classic Software Configuration Management (SCM)process, which utilizes a three-way merge to manage concurrent development.

The merge process involves three repositories:

The (Original|Received|Master|Parent) repository. The repository that you received before changed. You must keep it preciously unchanged.

The Modified repository. The repository that contains the customizations you made to the original repository.

The Current repository. Generally, the repository that is in production and where some customisations could have been performed by other people.

In a multiuser environment (MUDE), Developers check out the file and make changes locally. Then, these changes are automatically reconciled and merged into the master repository.

The Software Only Install type installs the Oracle Business Intelligence software binary

files in an Oracle home for later configuration as part of a Fusion Middleware

deployment.

After creating your base metrics, try using the Calculation Wizard to automate the process of creating time-series metrics or comparison metrics such as: Change, Percent Change, Index, and Percent. The Wizard may save you many hours of time and frustration, especially if you have to create more than a handful of these metrics. In addition, the Wizard allows you to include customized logic to handle nulls in the base metrics. You may refer to the Oracle documentation for further detail.

Metadata Repository Builder's Guide

http://download.oracle.com/docs/cd/E21764_01/bi.1111/e10540/toc.htm

http://download.oracle.com/docs/cd/E21764_01/bi.1111/e10540.pdf

Setting an Implicit Fact Column in the Subject Area

For each subject area in the Presentation layer, you can set an implicit fact column. The

implicit fact column is added to a query when it contains columns from two or more

dimension tables and no measures. The column is not visible in the results. It is used

to specify a default join path between dimension tables when there are several possible

alternatives or contexts.

With the advent of 11G, MapViewer is installed as part of Oracle BI Enterprise Edition and deployed in the same domain as Oracle BI EE on the Web application server.

Before content designers can create map views, in the Manage map Data Administration page, the metadata must be configured:

* layers (theme) and map (zoom level)

* the mapping between Oracle BI EE data and spatial data

Modeling Time Series Function in OBIEE

Modeling Time Series Data

Time series functions provide the ability to compare business performance with previous time periods, allowing you to analyze data that spans multiple time periods. For example, time series functions enable comparisons between current sales and sales a year ago, a month ago, and so on.

Because SQL does not provide a direct way to make time comparisons, you must model time series data in the Oracle BI repository. First, set up time dimensions based on the period table in your data warehouse. Then, you can define measures that take advantage of this time dimension to use the AGO, TODATE, and PERIODROLLING functions.

If you want to create a dynamic time-series reference such as the value of a measure as at this time last year, or over the past three months, or year-to-date, you can use one of the OBIEE time-series functions (AGO, PERIODROLLING, TODATE) to provide an offset value for a measure.

Figure:

Note: OBIEE 11g offered a bunch of improvements that were particularly aimed at Essbase, and other OLAP server, customers; the new hierarchical columns feature brought proper OLAP analysis to OBIEE, and coupled with OLAP-oriented features such as hierarchical prompts and selection steps, made OBIEE 11g a much more conducive environment for Essbase users.

There’s much better support for Essbase-native features such as value-based hierarchies, alternate hierarchies, multiple alias tables, UDAs and other Essbase artifacts, and the value-based hierarchy feature in particular is very welcome as it can avoid the need to completely re-import your Essbase database if your outline gains additional hierarchy levels.

So coupled with the new and improved visualization capabilities in OBIEE 11g, including maps, scorecards, improved dashboard controls, the whole new UI, improved BI Publisher and so on, there’s a lot to recommend OBIEE 11g to users of the “legacy” Hyperion tools looking for a bit of a refresh of their BI environment.

Note: This source should be combined with other sources at this level (check box)

Description: Check this box when data sources at the same level of aggregation do not contain overlapping information. In this situation, all sources must be combined to get a complete picture of information at this level of aggregation.

Note 2: To use a source correctly, the Analytics Server has to know what each source contains in terms of the business model. Therefore, you need to define aggregation content for each logical table source of a fact table. The aggregation content rule defines at what level of granularity the data is stored in this fact table.

Use the Content tab of the Logical Table Source dialog box to define any aggregate table content definitions, fragmented table definitions for the source, and Where clauses (if you want to limit the number of rows returned).