Download Oracle.1z0-591.CertKiller.2019-01-19.72q.tqb

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. B: Note: The Analytic Data Model (ADM) is an API used to access OLAP data and metadata. ADM is similar to JDBC, providing a single common API that hides most differences between OLAP data sources. Note 2: Data model for business intelligenceThe 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

Note 1: There are four types of variables that you can use:Session Repository Presentation Request Note 2: Session VariablesA 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. Incorrect answers:A: ETL Load Date is a DAC Source System Parameter.C: OLAP DSN is a Repository variable.

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.