Pass the Oracle Oracle Other Certification 1z0-591 Questions and answers with CertsForce

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.

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.

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

The relationship is defined at the model and mapping layer.

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.

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.

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.

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

The Oracle BI repository development process adheres to the classic Software Configuration Management (SCM)process, which utilizes a three-way merge to manage concurrent development.

The merge process involves three repositories:

The (Original|Received|Master|Parent) repository. The repository that you received before changed. You must keep it preciously unchanged.

The Modified repository. The repository that contains the customizations you made to the original repository.

The Current repository. Generally, the repository that is in production and where some customisations could have been performed by other people.

In a multiuser environment (MUDE), Developers check out the file and make changes locally. Then, these changes are automatically reconciled and merged into the master repository.