All 1z0-591 Test Inside Oracle Questions

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.

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

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.