1z0-591 Sample Questions Answers

The Oracle BI Presentation Services Administration page provides the Manage Map Data link. This link displays the Manage Map Data page, where you can manage the logical and display versions of the data from various physical data sources. This defines the layers that content designers use when creating map views. The data that is available for managing maps and data is stored in Oracle Database as part of MapViewer.

Using this page, you provide:

* (A) Logical names to prevent any existing BI column mappings and map analyses from breaking because of changes to the physical data or to the data source.

* Display names so that the geographic data is meaningful to end users.

Note: Administering Maps Using Administration Pages

For (C) –layers, see 3-7 below.

For (D) –import images, see 11-12 below.

To administer maps using Administration pages:

Sign in to Oracle Business Intelligence.

In the global header, click Administration.

Click the Manage Map Data link to display the Manage Map Data page.

Click the Layers tab.

Click the Import Layers button to display the Import Layers dialog.

In the dialog, select the connection and the layers that are needed for zooming and drilling. (This tab is not prepopulated by other selections on the Administration pages. You can use any layers or images with any map.)

Click OK when you have finished selecting layers that are appropriate for the subject area with which you are working.

Back on the Layers tab, select a layer, then click the Edit Layer button to display the Edit Layer dialog in which you associate layers with attribute columns so that you can display BI data in the map view.

Click OK when you have finished editing the layer.

You use this tab to associate layers with BI data. If you use the City column in multiple subject areas, then you must associate it with a layer for each subject area.

Click the Background Maps tab, then click the Import Background Maps button to display the Import Background Maps dialog.

In the dialog, select the connection and the main maps to use.

The connection that you select for the main map can be different from the connection for the layers or images.

Click OK when you have finished selecting main maps.

Back on the Background Maps tab, select a map, then click the Edit Background Map button to display the Edit Background Map dialog in which you name the map and specify the order of layers and their zoom levels.

Click OK when you have finished editing the map.

Optionally, click the Images tab, then click the Import Images button to display the Import Images dialog. You can import images if you plan to use them as a format on maps.

In the dialog, select the connection and the images to use.

Click OK when you have finished selecting images.

Click Back when you have finished working with the Administration page. Your changes are saved automatically.

A: OBIEE 11g is centred on WebLogic Server as the underlying application server architecture.

B: If you want to scale out this infrastructure, you would typically run the OBIEE 11g installer on a second server, and instead of choosing to do a new install, you’d choose to instead scale out the existing BI domain.

C: OBIEE Clustering – Approach of Oracle BI Server Load balancing/Failover

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.

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.

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.

NQSConfig.ini is the main configuration file of Bi Server and contains a lot of parameters.

The parameters in the Query Result Cache Section provide configuration information for Oracle BI Server caching. The query cache is enabled by default. After deciding on a strategy for flushing outdated entries, you should configure the cache storage parameters in Fusion Middleware Control and in the NQSConfig.INI file.

This warning indicates that the given column is only mapped to logical table sources that are disabled. The warning brings this issue to the repository developer's attention in case the default behavior is not desired.

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

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

B: The problem with caching of any kind is how to deal with stale data. How you decide to deal with this depends on how time critical your business intelligence queries happen to be. OBIEE provides a wide variety of mechanisms for dealing with stale data. The cache can be purged automatically at intervals. Caching can be enabled selectively for individual physical tables, so that data in a frequently updated table is never cached. OBIEE provides a set of ODBC procedures that can be called when ETL processes complete to programmatically purge designated tables. But, by far the best way to selectively purge the cache is to use an event polling table. This table is populated by the client database whenever changes are made to any table (by an ETL process for a data warehouse or by a table-based trigger for an OLTP database). At specified intervals the BI Server polls this event polling table and deletes from its cache any query results that are dependent on the changed data.

Example (see step 4 and 5 below): Getting Top-N Sales Reps for Year and Year-1

1. Under the “Business Model and Mapping” Layer, right click the “F1 Revenue” and select “New Object” -> “Logical Column…”

2. In the “Logical Column” Window give for Name: Year Ago Revenue as seen below:

3. Goto the “Column Source” Tab and select “Derived from existing columns using an expression” radio button then click on the “Edit Expression” icon.

4. Enter the following expression in the “Expression Builder” Window by selecting “Functions” in the “Category:” list, “Time Series Functions” in the “Functions:” list then “Ago” “Time Series Functions:” section.

5. Select the “<>” in the “Ago( )” function, then select “Logical Tables” in the “Category:” list, “F1 Revenue” in the “Logical Tables:” list, then double click the “Revenue” in the “Columns:” list.

Etc.

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.

The “Edit Column Formula” dialog box has a second,

very tiny tab called, “Bins.” You can use this tab to have OBIEE

build a CASE statement for you in a formula (you can also create

a CASE statement yourself by using one of the functions that

appears under “Expressions” if you want). A CASE statement is a

lot like an IF-THEN-ELSE statement, except that it’s a little easier

to read when you have multiple options. Basically, it puts values

in different buckets that you define.

Note:

Figure:

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

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

B: Click Refresh All from the Oracle BI menu in PowerPoint to refresh all the refreshable objects in the presentation.

C: Right-click Table and select Insert as List from the shortcut menu. The Edit Prompts and Levels dialog box appears. Accept the default options and click Insert.

Decrease query response time which will improve performance for Dashboards and Analysis.

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.

Dimensional Modeling - Slowly Changing Dimensions

* Type 1 - Overwrite Original Value

A change does not require tracking

* Type 2 - Add a new record

With Type II SCD, a new version of the dimension record (row) is created, and the existing version is marked as history.

Each row does not correspond to a different instance of an entity but a different “state”, a “snapshot” of the instance at a point in time.

Note: Tracking changes in dimension is referred in datawarehousing as slowly changing dimensions.

In the source system a lot of changes are daily made :

new customers are added,

addresses are modified,

new regional hierarchies are implemented,

or simply the product descriptions and packaging change.

These sorts of changes need to be reflected in the dimension tables and in several cases, the history of the changes also needs to be tracked.

By remembering history, we are then able to look at historical data and compare it to their current situation.

B: 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.

E: The database 11gR2 is required if you want to run the Oracle Business Intelligence Enterprise Edition Plus Samples

One Oracle Database Preinstalled and not hardened to host the schemas.

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.

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)

Open up the Administration tool, go to Manage then variables.

See screenshot below.

Then follow this picture to create a new Initialization Block.

Name your Initialization block init_block_test.

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.

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

Oracle Business Intelligence Enterprise Edition (OBIEE) Security is managed through:

a) BI Server Security Manager accessed through the BI Server Administration Tool.

* Set permission to business model, tables, columns and subject areas

* Specify filters to limit data accessible by users

* Set authentication options

b) BI Presentation administration accessed through Presentation Web Services.

* Manage Web groups and users

* Set Permissions for Web Catalog items

* Manage privileges and rights given to groups and users

* Control access to dashboards

c) Catalog Manager.

* Set permission for Web Catalog items (Dashboards and Dashboards pages)

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.

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

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