1z0-591 Exam Dumps - Oracle Business Intelligence Foundation Suite 11g Essentials

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

Query environment can be managed by setting query limits (governors) in the Repository (RPD) for particular Application Roles. You should always set query limits for particular application roles rather than for individual users.

Steps:

1. Login to Repository using OBIEE Admin Tool

2. Navigate to Manage > Identity

3. Go to Application Role tab, choose the role and double click on it to open.

4. Click on Permissions tab

5. Set the 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.

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.

A:

* Combining Relational and OLAP Data Sources: Oracle’s Common Enterprise Information Model allows users to combine data from a relational system and an OLAP source in a single calculation. For example, a user can compare sales forecasts from an Oracle CRM System with budget data from an Oracle Essbase planning application. To clients of the Common Enterprise Information Model, the forecast and budget data appear to be from the same logical source.

* The Essbase server provides advanced multi-user read and write capabilities, including data update and multi-user recalculation. Business users with front-end tools can write data back to a server and recalculate the data on a server using calculation scripts—key functionality to support sophisticated modeling and planning applications.

* Using aggregate storage, Essbase serves a wide range of analytic needs—financial analysis, planning, budgeting, sales analysis, marketing analysis, supply-chain analysis, and profitability analytics—all from a single analytic infrastructure.

Note 2: Data model for business intelligence

The most important component of business intelligence is the concept of 'data model'. data model determinde what kind of analysis that end user could do with the data. It is also an independant concept that could span across different vendor 's product.

Unlike data model of the transaction system, the typical analytic data model is often denormalized and store extra data for analytic query and better query performance while transaction data model use is often normalized and optimized for a few data read and write, which is implemented by jointing many tables.

The most common used analytic data model in business intelligence is call the 'Star schema' data model.

With the Oracle business intelligence system, We could define star schema and dimension data model in the 'logical layer' in the admin tools. The data model in OBIEE could span different data source in physical layer, which means OBIEE have the capability of building one logical data model which is actually connect to different database in the backend