06_Testing and Validating Repository

7/29/2019 06_Testing and Validating Repository

1/21

Testing and Validating a Repository

Copyright 2012, Oracle and/or its affiliates. All rights reserved.


2/21

Objectives

After completing this lesson, you should be able to execute the

steps to test and validate a repository.

Copyright 2012, Oracle and/or its affiliates. All rights reserved.6 - 2


3/21

Validating a Repository

The following steps validate whether a repository is constructed

correctly and yields the expected query results:

1. Checking a repository for consistency

2. Enabling logging

3. Loading a repository


4. Checking a repository by running analyses5. Inspecting the query log


4/21

ABC Example

Validate and test the SupplierSales business model before

making it available to users for querying.


SupplierSales is not available for queries.


5/21

Consistency Check

Is a feature of the Administration Tool that checks whether a

repository has met certain requirements, such as the following:

All logical columns are mapped directly or indirectly to oneor more physical columns.

All logical dimension tables have a logical key.


og ca a es ave a og ca o n re a ons p o ano er logical table.

There are at least two logical tables in the business model:

a logical fact table and a logical dimension table. Both can

map to the same physical table. There are no circular logical join relationships.

A subject area exists for the business model.


6/21

Use the File menu.

Checking Consistency

Check consistency for the entire repository or for individual

repository objects by using the following methods:

Use the Tools menu. Right-click objects.



7/21

Consistency Check Manager

Displays consistency check messages

Errors: Must be fixed to make the repository consistent

Warnings: Indicate conditions that may or may not beerrors

Best Practices: Are conditions that do not indicateinconsistencies



8/21

Using the validaterpd Utility to Check

Repository Consistency

You can use the validaterpd utility to check the validity of all

metadata objects in a repository on any platform supported by

the Oracle BI Server.



9/21

Marking a Business Model Available for Queries

When a business model is consistent, you can mark it as

available for queries.


SupplierSales is available for queries.


10/21

Confirming a Consistent Repository

When a repository is consistent, you receive the following

message:

Copyright 2012, Oracle and/or its affiliates. All rights reserved.6 - 1 0


11/21

Publishing a Repository

Use Fusion Middleware Control to publish a repository and

make it available for queries.

Click here first.


Current installed repository

Browse to upload

new repository.

Click to apply

changes.


12/21

Using FMW Control to Start OBI Components

Use the Overview

page to manage all

OBI components.


Use the Capacity

Management >

Availability page to

manage individual OBI

components.


13/21

Query Logging

Oracle BI Server provides a facility for logging query

activity at the individual user level.

Logging is intended for quality assurance testing,debugging, and use by Oracle Technical Support.

Query logging is normally disabled in production mode.


e query og e s name uery. og an s oca e

in the following directory:ORACLE_INSTANCE\diagnostics\logs\

OracleBIServerComponent\coreapplication_obis1


14/21

Setting a Logging Level

Open the repository in online mode and use the Identity

Manager to enable the logging level for individual users.


Set the logging level.


15/21

Logging Levels

Logging levels 1 and 2 are for BI Server administrators.

Repository name, business model

name, subject area name

SQL for the request using business

model names

All items for Level 1, plus those

mentioned below:

User name, session ID, and request ID

for each query

Level 2 LogsLevel 1 Logs


SQL for the request using physicaldata source syntaxQuery status (success, failure,termination, or timeout)

Queries issued against the cacheElapsed times for query compilation,

execution, query cache, and back-end

database processing

Number of rows returned from a

physical database

Number of rows returned to the

client


16/21

Validating by Using the Analysis Editor

Use the Analysis Editor to validate the Presentation layer

display, execute analyses, and check query results.


.

Execute analyses

and check results.


17/21

Inspecting the Query Log

Use Fusion Middleware Control Log Viewer to search for and

view query log entries:



18/21

Viewing Log Messages

Use Fusion Middleware Control Log Viewer to view the log files

in their entirety:

General query Information


Logical SQL


19/21

Oracle BI SELECT Statement: Syntax

Basic syntax for an Oracle BI SELECT statement:

SELECT Columns

FROM Catalog folder or tablesWHERE Filtering conditions

GROUP BY (Optional, special use)

ORDER BY Columns (optional)


Example

SELECT Region, Dollars

FROM SupplierSales

WHERE Year = 1999ORDER BY Dollars desc


20/21

Oracle BI SELECT Statement

Compared with Standard SQL

Oracle BI SELECT statements differ from standard SQL in the

following ways:

No join information is required. Join conditions are predefined in the repository.

Join conditions supplied in a query are ignored.


.

Aggregation rules are known to the server, and aggregationis performed automatically.

No GROUP BY clause is required.

If aggregated data is requested in the SELECT statement, a

GROUP BY clause is automatically assumed by the server.

No DISTINCT keyword is required.

Oracle BI Server issues SELECT DISTINCT to eliminate

duplicate rows automatically.


21/21

Summary

In this lesson, you should have learned how to execute the

steps to test and validate a repository.


06_Testing and Validating Repository

Documents

Transcript of 06_Testing and Validating Repository