Oracle 1z0-591 Dumps

OBIEE - Grain (Level of summarization)

Grain definition in the context of OBIEE.

The following list describes the different grains in navigating a query:

* Aggregation grain. The grain of the aggregate source of from a level based metrics

* Query grain. The grain of the request.

* Time Series grain. The grain at which the time series function aggregation is requested.

* Storage grain. The query in the example can be computed from daily sales or from monthly sales, or from quarterly sales.

Note:

The aggregation grain is defined in the content tab of the logical table source.

When the query grain match the aggregation grain of a logical table source, this one is used to create the physical query.

B: Example:

1. Configure the new source table to have the 'logical level' under the content set to 'Countries' (the summarized level)

b

2. Do the similiar setting for dimension table

Now when user query the data at 'Counties' level, the query will be redirected to these summary table instead of the more detail fact table

Note: Aggregate tables are Physical tables that store Aggregates of measures across multiple levels of a Hierarchy.

Security Realms are an Oracle Platform Security Services concept and bring together sets of users, groups, providers and so on for a WebLogic domain.

All metadata for cubes and dimensions is stored in the Oracle database and revealed in the data dictionary views, so that you can query the entire business model in SQL.

You can control the way that the interface for Oracle BI EE is displayed to users by creating skins and styles.

While skins and styles are typically used to customize the look and feel of analyses and dashboards by providing logos, color schemes, fonts, table borders, and other elements, they can also be used to control the position and justification of various elements by including specialized style tags in the relevant style sheet (.css) file.

You can check the directory skin location with a right click on a OBIEE dashboard page, select show source code and search “custom.css”.

You should use a logical column (not physical). In fact,in the Explanation of the exam, it displays a logical column.

Content Tab

Aggregation Content

You can define the aggregation (ie the group by) of:

by hierarchy level

by logical column

It helps you to define an aggregate navigation

Note: logical table source

Logical table sources define the mappings from a single logical table to one or more physical tables. A logicaltable contains one or more logical table source. The mapping between physical columns and logical columns are done in this element.

The definition of the logical table source is used:

to specify transformations/calculations (in the column mapping tab),

to enable aggregate navigation and fragmentation (in the content tab)

The Content tab of the Logical Table Source is used to define :

any aggregate table content definitions (specify the grain of the physical tables),

fragmented table definitions for the source,

and WHERE clauses (if you want to limit the number of rows returned).

An action link is a link to an action that you have embedded in an analysis, dashboard page, scorecard objective, scorecard initiative, or KPI that, when clicked, runs an associated action.

Ragged Hierarchies are hierarchies where some routes down the hierarchy are longer than others; for example, you may have an organizational hierarchy for salespeople where the overall boss has two assistant managers, one of them works on their own and another has three sales managers under them; some of those sales manager may have sales staff under them, and some sales staff may have trainees under them.

Screenshot below.

In a Star Schema the dimensional tables does not need to be normalized.

A Snowflake Schema is a modified Star Schema that has normalized the dimensional tables.

Note: A level-based measure is a column whose values are always calculated to a specific level of aggregation.

The calculation of this measure is independent of the query grain and used always the aggregation grain of the logical column.

Level-based measures allow :

* to return data at multiple levels of aggregation (the query grain and the level-based column grain) with one single query

* to create share measures (percentage), that are calculated by taking some measure and dividing it by a level-based measure. For example, you can divide salesperson revenue by regional revenue to calculate the share of the regional revenue each salesperson generates.

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

Query Limits. You can limit queries by the number of rows received, by maximum run time, and by restricting to particular time periods. You can also allow or disallow direct database requests or the Populate privilege.

See figure below.

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.

In a standard OBIEE implementation, we generally want to purge and re-build the cache after every ETL (extract, transform, and load) run.

You can specify a Driving table parameter in a complex join.

Driving tables are for use in optimizing the manner in which the Oracle BI Server processes cross-database joins when one table is very small and the other table is very large.

The BI Server will query the driving table (the small one) and will get a list of values. The BI Server will then generate a second SQL using a parameterized IN list with the values from the first query.

Specifying driving tables leads to query optimization only when the number of rows being selected from the driving table is much smaller than the number of rows in the table to which it is being joined.

You can nest presentation folders in two ways.

1) You can enter a hyphen and a greater than sign in the description field of the table to achieve the result.

2) Or, prefix the name of the presentation folder to be nested with a hyphen and a space and place it after the folder in which it nests to achieve the same result as shown below.

Result

CurrentDay and CurrentMonth can be calculated by a sql statement.

Note:

REPOSITORY VARIABLE(DYNAMIC)

· Initialized when BI server is started

· Assigned value dynamically based on the result of a query

· Value is dependent of the sql provided in Initialization Block

Create a dynamic variable and provide a Name and Default Initializer.Create a new initialization block by clicking on the New button in the above screen.

Provide Intialization Block variable Name

The principal connection to an OBI Server inside the Oracle BI System is made through an Odbc Connection.

OBI Server can handle multiple repository but you can connect to only one at the same time by DSN Odbc Connection. Therefore, you must set up an ODBC connection for each repository.

Note:

At the highest level, an OBIEE Metadata Repository includes three layers of information:

1.

First, a Physical layer is defined. The metadata layer identifies the source data.

2.Second, a Business Model and Mapping layer is defined. This metadata layer organizes the physical layer into logical categories and records the appropriate metadata for access to the source data.

3.Finally, the Presentation layer is defined. This metadata layer exposes the business model entities for end-user access.

Before you can run Oracle Business Intelligence 11g Installer, you must first create

required Oracle Business Intelligence schemas in an unhardened database. You use

a tool called the Repository Creation Utility (RCU) to create these schemas with

the appropriate permissions and data.

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

Consistency check is one of the process to check whether a repository is yielding proper results in Answer reports. It checks whether;* All logical columns are mapped correctly to physical columns (B).* All logical dimension tables have a logical key.* There are at least two logical tables in the business model; one is a logical fact table, the other is logical dimension table with join condition.* There are no circular logical join relationships.* A presentation catalog exists for the business model.

Users in Oracle BI Answers can create queries that span multiple subject areas, as long as the subject areas correspond to the same business model.

You have three sort of fragmentation:

Fact-based / Dimension-based fragmentation

Content-based / Value-based fragmentation

Level-based fragmentation / aggregate navigation

You can combine the techniques above to construct powerful design that are known as Complex partitioning / fragmentation. When you fragment a dimension, you are automatically in a complex fragmentation.

Note 1: OBIEE offers two calculation types for measure in the repository:

logical

physical

You can define calculations in either of the following ways:

* Before the aggregation, in the logical table source.

* After the aggregation, in a logical column derived from two other logical columns. For example: sum(col A) * sum(col B)

Note 2: A measure column is a column unlike the baseline column that has a default aggregation rule defined in the Aggregation tab of the Logical Column dialog in the repository.

Measure columns always calculate the aggregation with which they are defined.

Measures need to be defined in a logical fact. Any column with an aggregation rule is a 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.

Aggregate Persistence Wizard automates the creation and initial population of aggregates, persists them in a back-end database and configures the BI Server metadata layer so that they’re used when appropriate.

Initialization blocks are used to initialize dynamic repository variables, system session variables, and nonsystem session variables.