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

The Oracle Business Intelligence (BI) Administration Tool can be used to build, modify, enhance, and manage an Oracle BI repository.

C: To add a new user to a repository

1 Open a repository in the Administration Tool.

2 Display the security manager by selecting Manage > Security.

3 Select Action > New > User to open the User dialog box.

4 Type a name and password for the user.

5 If you want to log queries for this user in the query log, change the query logging level to 1 or 2.

6 Click OK.

This creates a new user with default rights granted to it.

Note: What is Oracle BI Admin Tool/Oracle Business Intelligence Administration Tool?

Oracle Business Intelligence Administration Tool is Used to manage OBIEE server

Available only for Windows operating systems.

A Windows application that allows the BI Server administrator to create & edit repositories.

Can edit repositories in either online or offline mode.

Having a session manager and a cache manager in online mode.

A single query can be performed accessing data from both tables through a join on the columns in the foreign key relation.

Priority group

You can set priority group numbers to determine which logical table source should be used for queries for which there is more than one logical table source that can satisfy the requested set of columns.

For example, you might have user queries that can be fulfilled by both a data warehouse and an OLTP source. Often, access to an operational system is “expensive,” while access to a data warehouse is “cheap.” In this situation, you can assign a higher priority to the data warehouse to ensure that all queries are fulfilled by the data warehouse if possible.

Note that the priority group of a given logical table source does not always ensure that a particular query will be fulfilled by that source.

Priority Group Designation

0 the highest-priority source (the default)

1 a lowest-priority source

Identity Store: It is directory server to perform the authentication. It contains user name , password and groups membership information .When a user name and password combination is entered at log in, the authentication provider searches the identity store to verify the credentials provided.

See figure below.

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.

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

C: The wizard then shows me a preview of the script it’s going to generate, and asks me if I want to create any more summaries. Here’s how the preview script looks – note that it’s not SQL, it’s a script language that the BI Server understands and uses as the specification for an aggregation job, which it then turns into separate CREATE TABLE, INSERT … SELECT and so on SQL statements, “optimized” for the particular back-end database platform.

Script example:

"ag_Items"

for "Seminar - Complete"."Items"("Quantity")

at levels ("Seminar - Complete"."Customerdim"."State", "Seminar - Complete"."Productdim"."Category", "Seminar - Complete"."Timedim"."Year")

using connection pool "custdw"."CUSTDW_Pool"

in "custdw".."CUSTDW";

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.

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.

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.

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.

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.

The Repository can be configured within the Enterprise Manager. See Note 1 below.

Note 1: Once you’ve locked the Oracle BI Domain, you would then use the same screen back in Enterprise Manager to browse and select the RPD file, and then enter the password, twice.

Once you’ve entered these details you would then press the Apply button, to save the changes. At this point, the RPD gets a sequence number after it, and it’s displayed as the current default online repository for the Oracle BI Domain.

Note 2: An OBIEE 11g system (or “Oracle BI Domain”) is generally managed through a combination of Oracle Enterprise Manager Fusion Middleware Control, part of the Enterprise Manager “family”, or through WebLogic Server Scripting Tool (WLST) scripts. Each Fusion Middleware Control instance as shipped with OBIEE 11g controls a single Oracle BI Domain (DEV, or PROD for example), and is installed along with WebLogic Server Admin Console in the WebLogic Admin Server, one of the two JVMs (the other being the managed server) that gets installed by default with OBIEE 11g. The screenshot below shows Fusion Middleware Control showing the status of the BI Server, Presentation Server and other system components within the installation.

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