Free and Premium Oracle 1z0-591 Dumps Questions Answers

BSO is preferred to ASO in the following scenarios:

* Top-down planning and allocation (Sales Forecasting)

* Cost Allocations across products and customers (Profitability Analysis)

* Currency conversion, inter-company eliminations(Financial consolidations)

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

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

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

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

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.

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

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.

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.

BI EE uses the ADM driver to extract the data from HFM.

Note: HFM (Hyperion Financial Management)

Example:

I EE connects to HFM through JavaHost. So, the setup for configuring the connectivity is to basically make the EPM environment variables available for access to BI EE. Before making the changes, there are a couple of things to be aware of

1. Ensure that DCOM is enabled on the BI Server machine. This is needed for HFM client to work/connect properly with HFM Server.

2. Ensure that HFM Client is installed.

The above assumes EPM 11.1.2.x version. If you are on Hyperion 9.3.3, then you need to have the ADM drivers installed manually. All of this is documented clearly. So, rather than re-iterating that i will just point to the link here. Ensure that you follow all the steps mentioned in the docs else you will have issues in the connectivity. Once all the pre-requisite steps are done, we start off with the metadata import process.

Denormalization is the process of intentionally backing away from normalization to improve performance by suppressing join and permitting the use of star transformation technique.

Denormalization should not be the first choice for improving performance and should only be used for fine tuning of a database for a particular application.

Horizonal Scaleout of System Components

* Used for adding additional managed servers (Java components) and

system components to an existing cluster

* Used for scalability and failover

* Set up via the Universal Installer > Scale Out BI System option

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

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.

--------

In an Ibor or Agent, in the 'Destinations' tab you can set the 'Specific Devices' However, it is a Device or Delivery Profile the one used for alerts, see this OBIEE guide:

---------------x--------------

User's Guide

page 218

What Are Devices and Delivery Profiles?

Devices and delivery profiles control how you will be reached when an alert is

generated by an agent and which devices receive the content:

¦ Device — A device is the medium used to deliver content to you. The content of

an agent can be delivered to a range of devices as an e-mail or SMS message.

¦ Delivery profile — A delivery profile specifies which devices to use to deliver

content to you, based on the priority of the content. You can define several

delivery profiles to meet your needs, and switch

---------------x--------------

A: Much of the configuration of OBI that used to be done in the NQSConfig.ini files can now be done using this front end console, which in turns updates the NQSConfig.ini file. Things in the NQSConfig.ini file that are set by EM are noted in the file with '# This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager'. Some things that needs to be setup manually in the NQSConfig.ini file are:

1. Usage Tracking

2. Dynamic Libraries

3. Query Optimization Flags

4. MDX Member Name Cache Section (SAP BW)

5. More specific General Settings where EM doesn't contain the level of detail required

D: Cache Management Techniques include

• Inspecting the cache reports

• Configuring the cache parameters

• Setting caching and cache persistence for tables

• Using the Cache Manager

• Inspecting SQL for cache entries

• Modifying the Cache Manager column display

• Purging the cache entries manually using the Cache Manager

• Purging the cache entries automatically

• Using event polling tables

• Seeding the cache

A data warehouse is a database used for reporting and data analysis. It is a central repository of data which is created by integrating data from multiple disparate sources. Data warehouses store current as well as historical data and are commonly used for creating trending reports for senior management reporting such as annual and quarterly comparisons.

You do not use ODBC DSN to compare repositories.

Note: When an ODBC based application connects to a database, it connects to a logical name, the Data Source Name (DSN), which identifies the datasource to which it wants to connect.

Some external repository of configuration information holds the various DSN values that are available, together with the necessary configuration and control information needed by the ODBC driver to establish a connection and manage usage of the data source.

The DSN (data source name) is a data structure that contains the information about a specific data source (database, …), typically used by an ODBC driver to be able to connect to it.

The DSN contains information about the data source such as:

the name,

the directory,

and the driver.

On Windows, the DSN also specifies the ODBC driver to be used to access the database.

It is a best practice to create aliases for all tables. Aliases are created in the Physical Layer of the repository. Some of the benefits of using aliases are given below:

(A) * An alias is used to avoid circular joins and to configure self joins.

* You can create a join relationship which is different than the actual foreign key relationship in the database. This helps in defining relationships to meet business model criteria.

* Aliases can function in numerous ways to define business model e.g. a table can act both as a dimension and a fact using aliases.

(B) * You can rename aliases to make physical and business model easier to understand.

Purge and reseed once a week after the reports have run to improve report response time.

There are static and dynamic repository variables.

Note:

Variables in the Oracle BI Server can be either repository or session variables, and are defined using the Variable Manager within the Oracle BI Administrator (Manage > Variables).

This brings up the Variable Manager, that divides variables out into repository and session variables, with a further subdivision into static and dynamic repository ones and system and non-system session ones. You can also define variables at the Presentation Server level, these are scoped to individual dashboards and are used amongst other things for setting dashboard prompt values and integrating the dashboard with BI Publisher parameters. Here’s a screenshot of a typical Variable Manager screen.

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.

In online mode, you connect to a catalog on a running web server. In this mode your permissions are applied, you can select a locale, and you can see the effects of any localization on the catalog. You can see only those objects for which you have the appropriate permissions. Both Presentation Services and the web server must be running for you to open catalogs in online mode.

Use online mode when you want to make minor incremental changes or additions to the catalog, such as changes to permissions, updates to a single object, or migration of new objects to a production environment.

Note:

* You can open a catalog in one of two modes — online or offline. Both modes can operate against an actual production catalog, with no need for any downtime.

* Repository changes can be done in either online

or offline mode. Online mode is when BI Server

is actively reading the repository file (when a

user is logged in). Offline is when BI Server is

idle. Best practice is to develop in Offline mode.

Minor changes can be made when in online

mode.

Note 1: There are four types of variables that you can use:

Session

Repository

Presentation

Request

Note 2: Session Variables

A session variable is a variable that is initialized at login time for each user. When a user begins a session, the Oracle BI Server creates a new instance of a session variable and initializes it.

There are as many instances of a session variable as there are active sessions on the Oracle BI Server. Each instance of a session variable could be initialized to a different value.

There are two types of session variables:

System — A session variable that the Oracle BI Server and Oracle BI Presentation Services use for specific purposes.

System session variables have reserved names that cannot be used for other kinds of variables (such as static or dynamic repository variables and non-system session variables).

Non-system — A system variable that the administrator creates and names. For example, the administrator might create a SalesRegion non-system variable that initializes the name of a user's sales region.

The administrator creates non-system session variables using the Oracle BI Administration Tool.

Screenshot below.

Object-level security controls the visibility to business logical objects based on a user's role. You can set up object-level security for metadata repository objects, such as subject areas and presentation folders, and for Web objects, such as dashboards and dashboard pages, which are defined in the Presentation Catalog.

1) Business logic object

This controls access to objects, such as:

* subject areas

* presentation tables

* presentation columns

For example, users in a particular department can view only the subject areas that belong to their department.

2) Web object security

This provides security for objects stored in the Web Catalog, such as dashboards, dashboard pages, folders, and reports. You can view only the objects for which you are authorized. For example, a mid-level manager may not be granted access to a dashboard containing summary information for an entire department.

In OBIEE cache will be stored as files on the Hard Disk of the OBIEE Server in the form of files.