Oracle Warehouse Builder 10g Implementation Part 1 · PDF fileOracle Warehouse Builder 10g:...

Oracle Warehouse Builder 10g: Implementation Part 1Volume I • Student Guide

D18398GC10

Edition 1.0

June 2006

D46578

®

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y

THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS CLASSROOM ONLY. COPYING eKIT MATERIALS FROM THISCOMPUTER IS STRICTLY PROHIBITED

Copyright © 2006, Oracle. All rights reserved.

Disclaimer

This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization of Oracle.

The information contained in this document is subject to change without notice. If you find any problems in the document, please report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not warranted to be error-free.

Restricted Rights Notice

If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTSThe U.S. Government’s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.

Trademark Notice

Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

AuthorsMolly CorreaRichard Green

Technical Contributorsand Reviewers

David AllanSharath BhujaniMaria BillingsMichelle BirdHerbert BradburyDairy ChanJean-Pierre DijcksNancy GreenbergJoe KleinDavid LastJohn LeighBen LoperPaul NarthPadu PotineniJohn PotterBrian PottleKasturi ShekharPuja SinghDick WhittingtonFrank YangOWB Professional Community, EMEA & Worldwide (via Jon Ainsworth, Tony Carpenter)

PublisherSujatha Nagendra

EditorsAju KumarNavratan Singh

Graphic SpecialistSamir Mozumdar

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


iii

Contents Preface I Introduction

Lesson Objectives I-2 Course Objectives I-3 Agenda: Day 1 I-4 Agenda: Day 2 I-5 Agenda: Day 3 I-6 Appendixes I-7 Questions About You I-8 Summary I-9

1 Setting Up and Starting Warehouse Builder Objectives 1-2 What Is Oracle Warehouse Builder? 1-3 Producing Quality Information 1-4 New Segmentation of OWB Functionality 1-5 BI Environment from an OWB Perspective 1-7 OWB Sources and Targets 1-8 Installing OWB 1-9 Hardware and Software Requirements 1-10 Supported and Certified Versions of Oracle RDBMS 1-11 Software Versions Compatible with Warehouse Builder 1-12 OWB Product Components 1-13 Installing and Configuring OWB 1-14 Configuring OWB 1-15 Classroom Stand-alone Configuration 1-16 OWB 10g R2 Default Installation with a Single Repository 1-17 Target Users 1-18 Logging In to OWB Design Center 1-19 Practice 1-1: reating a Repository Owner and User 1-20 Projects 1-21 Organizing Your Work in Projects 1-22 Concurrent Users per Project with Object Locking 1-23 Multiple User Access 1-24

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


iv

Design Center 1-25 Objects Within a Project 1-26 Objects Within a Module 1-31 Locations, Connectors, and Control Centers 1-35 Global Explorer Objects 1-37 Creating a Project 1-38 Setting Project Preferences 1-39 Summary 1-41 Practice 1-2: Invoking OWB and Opening a Project 1-42

2 Introducing OWB 10g R2 Architecture and Configuration Objectives 2-2 Process Flow of Design and Deployment 2-3 OWB 10g R2 Repository Default Installation 2-5 OWB 10g R2 Repository: Design Phase 2-6 OWB Design Components 2-7 OWB 10g R2 Repository: Run Time 2-9 OWB Run-Time Components 2-10 Loose Coupling of Metadata with Physical Implementations 2-12 Multiple Named Configurations: Preview 2-13 OWB Mapping 2-14 Executing a Mapping at a Target Location 2-15 Classroom Stand-alone Configuration 2-16 Independent Versus Dependent Marts 2-17 Independent Data Mart 2-18 Dependent Data Mart 2-19 Purpose of a Staging Area 2-20 Data Staging Area 2-21 Remote Staging Model 2-22 On-Site Staging Model 2-23 Purpose of an Enterprise Model 2-24 Course: Predefined and New Objects 2-25 OMB*Plus tcl Scripting Within Design Client 2-26 Launching OMB*Plus from the Command Line 2-27 Summary 2-28 Practice 2-1: Importing Metadata 2-29

3 Defining Source Metadata Objectives 3-2 Course Progress Report 3-3 Metadata to Data 3-4

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


v

Source Module 3-5 Lesson Data Sources 3-6 Creating a Flat File Source Module 3-7 Using the Create Module Wizard 3-8 Create Module Wizard: Name and Description 3-9 Create Module Wizard: Connection Information 3-10 Editing File System Location 3-11 Create Module Wizard: Summary 3-12 Metadata to Data 3-13 Import Metadata Wizard: Welcome 3-14 Importing from Flat Files 3-15 Selecting the Flat Files 3-16 Collecting Geography Metadata Information 3-17 Flat File Sample Wizard: Welcome 3-18 Describing the File 3-19 Record Organization 3-20 Selecting the File Format 3-22 File Layout 3-23 Modifying Field Information 3-24 Summary for Geography Metadata Sampling 3-25 Practice 3-1: Create a Flat File Source Module 3-26 Lesson Data Sources 3-27 Creating an Oracle Source Module 3-28 Create Module Wizard: Name and Description 3-29 Create Module Wizard: Connection Information 3-30 Editing the Oracle Database Location 3-31 Finishing Module Creation and Proceeding to Import 3-32 Import Metadata Wizard: Filter Information 3-33 Selecting the Tables for Import 3-34 Completing the Metadata Import 3-35 Examining the Imported Metadata 3-36 Viewing Data Using the Data Viewer 3-37 Difference Between Obtaining Relational and Flat File Source Metadata 3-38 Summary 3-39 Practice 3-2: Create a Relational Database Source Module 3-40

4 Ensuring Data Quality Using Data Profiling Objectives 4-2 Course Progress Report 4-3 What Is Data Profiling? 4-4 Steps in Data Profiling 4-5

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


vi

Creating a Data Profile 4-6 Create Data Profile Wizard: Name and Description 4-7 Create Data Profile Wizard: Select Objects 4-8 Create Data Profile Wizard: Summary 4-9 Steps in Data Profiling 4-10 Profiling the Data Using the Data Profile Editor 4-11 Data Profile Setup 4-12 Preparing the Profile 4-13 Profiling Initiated 4-14 Retrieving Profile Results 4-15 Practice 4-1: Profile the Data 4-16 Steps in Data Profiling 4-17 Types of Profiling 4-18 Attribute Analysis 4-19 Attribute Analysis: Glimpse of the Table Data 4-20 Attribute Aggregation Analysis 4-21 Aggregation Graphical Results 4-22 Determining the Six-Sigma Score 4-23 Attribute Data Type Analysis 4-24 Attribute Domain Analysis 4-25 Attribute Unique Key Analysis 4-26 Referential Analysis 4-27 Property Inspector 4-28 Performing Referential Analysis 4-29 Referential Analysis: Noncompliant 4-30 Joins Subtab on the Referential Page 4-31 Functional Dependency Analysis 4-32 Performing Functional Dependency Analysis 4-33 Summary 4-34 Practice 4-2: View and Analyze the Profile Results 4-35

5 Defining Staging Metadata and Mapping Tables Objectives 5-2 Purpose of a Staging Area 5-3 Defining a Staging Area Warehouse Module 5-4 Course Progress Report 5-5 Creating the Target User 5-6 Create User Wizard: Select DB User to Register 5-7 Create User Wizard: Check User as Target Schema 5-8 Creating the Warehouse Target Module 5-9 Create Module Wizard: Name and Description 5-10

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


vii

Create Module Wizard: Connection Information 5-11 What Are External Tables? 5-12 Creating an External Table 5-13 Create External Table: Name and Description 5-14 Create External Table: File Selection 5-15 Create External Table: Locations 5-16 Configuring External Tables 5-17 Practice 5-1: Overview 5-18 Practice 5-1: Create an External Table 5-19 Metadata to Data 5-21 Building a Mapping 5-22 Designing the LOAD_STG_GEOG Mapping 5-23 OWB Mapping Editor 5-24 Mapping Editor User Interface 5-25 Building a Mapping 5-26 Choosing the External Table 5-27 Creating a Staging Table 5-28 Adding an Attribute 5-29 Using a Constant Operator 5-30 Using the Expression Builder to Define a Constant Operator 5-31 Using a Filter Operator 5-32 Using the Expression Builder to Define a Filter Condition 5-33 Using a Joiner 5-34 Key Lookup Operator 5-35 Key Lookup Condition 5-36 Set Operation Operator 5-37 Building a Mapping 5-38 Mapping Source Columns to the Target 5-39 Using the Create and Bind Option to Create the Repository Table 5-40 Setting Load Type to TRUNCATE/INSERT 5-41 Synchronizing Operators and Repository Objects 5-42 Building a Mapping 5-43 Validating the Mapping 5-44 Generating the Mapping 5-45 Building a Mapping 5-46 Deploying a Mapping 5-47 Building a Mapping 5-48 Executing a Mapping 5-49 Metadata to Data 5-50 Viewing the Data Using Data Viewer 5-51 Pluggable Mappings 5-52

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


viii

Advantages of Pluggable Mappings 5-53 Example of a Pluggable Mapping 5-54 Target Load Ordering 5-55 Overriding the Default Load Order 5-56 Summary 5-57 Practice 5-2: Create a Simple Mapping from Source Objects to the Target 5-58

6 Deriving Data Rules and Running Correction Mappings Objectives 6-2 Course Progress Report 6-3 Lesson Progress Report 6-4 Data Rules 6-5 Deriving Data Rules 6-6 Derive Data Rule Wizard: Welcome 6-7 Derive Data Rule Wizard: Name and Description 6-8 Derive Data Rule Wizard: Define Rule 6-9 Derive Data Rule Wizard: Summary 6-10 Examining the Data Rule Panel 6-11 Lesson Progress Report 6-12 Creating Corrections Using the Create Correction Wizard 6-13 Create Correction Wizard: Select Target Module 6-14 Create Correction Wizard: Select Objects 6-15 Create Correction Wizard: Select Data Rules 6-16 Create Correction Wizard: Verify and Accept Corrected Tables 6-17 Create Correction Wizard: Constraints Tab 6-18 Create Correction Wizard: Choose Data Correction Actions 6-19 Lesson Progress Report 6-20 Examining the Correction Module 6-21 Examining the Generated Correction Mapping 6-22 Examining the Transformations Node 6-24 Summary 6-25 Practice 6-1: Deriving Data Rules and Creating Correction Mappings 6-26

7 Defining a Relational Dimensional Model Objectives 7-2 Course Progress Report 7-3 Lesson Scenario 7-4 Classifying the Data 7-5 Dimension Tables 7-6 Determining Granularity 7-7 Dimensional Design Using OWB 7-8

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


ix

Defining Dimensions 7-9 Creating a Dimension Using the Wizard 7-10 Create Dimension Wizard: Name and Description 7-11 Create Dimension Wizard: Storage Type 7-12 Create Dimension Wizard: Dimension Attributes 7-13 Create Dimension Wizard: Levels 7-14 Create Dimension Wizard: Level Attributes 7-15 Create Dimension Wizard: Data Policy 7-16 Create Dimension Wizard: Precreate Settings 7-17 Create Dimension Wizard: Dimension Creation Progress 7-18 Configuring a Dimension 7-19 Practice 7-1: Create a Dimension Using the Wizard 7-20 About the Data Object Editor 7-21 Detail View 7-22 Creating or Editing a Dimension Using the Data Object Editor 7-23 Creating a Dimension Using the Editor 7-24 Dimension Details: Name Tab 7-25 Creating a Dimension Role 7-26 Dimension Details: Storage Tab 7-27 Dimension Details: Attributes Tab 7-28 Dimension Details: Levels Tab 7-29 Dimension Details: Hierarchies Tab 7-30 Dimension Details: SCD Tab 7-31 Relational Implementation: Star 7-32 Relational Implementation: Snowflake 7-33 Binding 7-34 Autobinding 7-35 Manual Binding 7-36 Unbind 7-38 Dimension Details: Data Viewer Tab 7-39 Practice 7-2: Create a Dimension Using the Editor 7-40 Creating the Time Dimension by Using the Time Wizard 7-41 Create Time Dimension Wizard: Name and Description 7-42 Create Time Dimension Wizard: Storage 7-43 Create Time Dimension Wizard: Data Generation 7-44 Create Time Dimension Wizard: Levels 7-45 Create Time Dimension Wizard: Precreate Settings 7-46 Create Time Dimension Wizard: Progress Panel 7-47 Create Time Dimension Wizard: Summary 7-48 Practice 7-3: Create a TIMES Dimension Using the Time Wizard 7-49 Defining a Cube Using the Wizard 7-50

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


x

Create Cube Wizard: Name and Description 7-51 Create Cube Wizard: Storage Type 7-52 Create Cube Wizard: Dimensions 7-53 Create Cube Wizard: Measures 7-54 Create Cube Wizard: Summary 7-55 Editing a Cube Using the Data Object Editor 7-56 Assigning Roles 7-57 Configuring Cubes 7-58 Practice 7-4: Create a Cube Using the Editor 7-59 Designing ETL Mappings 7-60 Mapping to Load the PRODUCTS Dimension 7-61 Mapping to Load the SALES Cube 7-62 Pluggable Mapping 7-64 Generating the Mappings 7-65 Summary 7-66 Practice 7-5: Design ETL Mappings 7-67

8 Handling Slowly Changing Dimensions Objectives 8-2 What Is a Slowly Changing Dimension? 8-3 Types of Slowly Changing Dimensions 8-4 Type 1 SCD: Does Not Store History 8-5 Type 2 SCD: Preserves Complete History 8-6 Type 3 SCD: Stores Only the Previous Value 8-7 Creating a Type 2 SCD Using the Dimension Editor 8-8 Creating a Type 2 SCD 8-9 Mapping to Load the Type 2 SCD 8-13 Creating a Type 2 SCD Using the Wizard 8-14 Dimension Operator in a Mapping 8-15 Group Properties in the Dimension 8-16 Creating a Type 3 SCD 8-17 Attributes in a Type 3 SCD 8-18 Summary 8-19 Practice 8-1: Handling Slowly Changing Dimension 8-20

9 Using Process Flows Objectives 9-2 Course Progress Report 9-3 Process Flow Concepts 9-4 Creating a Process Flow Module 9-5 Creating a Process Flow Package 9-6

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


xi

Creating a Process Flow 9-7 Process Flow Editor 9-8 Types of Activities 9-9 Adding a Fork Activity 9-10 Adding a Mapping Activity 9-11 Adding an And Activity 9-12 Adding End Activities 9-13 Creating Transitions Between Activities 9-14 Transition Conditions 9-15 Generating the Process Flow 9-16 Practice 9-1: Create the LOAD_SALES_WH Process Flow 9-17 New Concepts in Process Management 9-18 Creating Activity Templates 9-19 Process Flow Activities 9-21 Creating a Variable 9-22 Assign Activity 9-23 Data Auditor 9-24 For Loop Activity 9-25 Route and While Loop Activities 9-26 Manual Activity 9-27 Notification Activity 9-28 Set Status Activity 9-29 SQLPLUS Activity 9-30 Wait Activity 9-31 Scheduling Concepts 9-32 Creating a Schedule Module 9-33 Creating a Schedule 9-34 Create Schedule Wizard: Name and Description 9-35 Create Schedule Wizard: Start and End Time 9-36 Create Schedule Wizard: Frequency and Repeat Interval 9-37 Monthly Schedule 9-38 Editing a Schedule 9-39 Schedule Example 9-40 Associating Executable with a Schedule 9-41 Assigning a Schedule to an Executable Object 9-42 Summary 9-43 Practice 9-2: Create a Schedule 9-44

10 Deploying, Loading, and Viewing Data Objectives 10-2 Course Progress Report 10-3

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


xii

Logical Versus Physical 10-4 Physical Implementation 10-5 Configuring for Physical Implementation 10-6 Accessing Object Configuration 10-7 Deployment Concepts 10-8 Registering Locations 10-9 Unregistering Locations 10-10 Configuration and Control Center 10-11 Active Configuration 10-12 Control Center and Locations 10-13 Control Center Manager Components 10-14 Invoking the Control Center Manager 10-15 Control Center Manager Interface 10-16 Default Action and Deploy 10-17 Deploy Options 10-18 Asynchronous Deployment and Execution 10-19 Deployment Tools Preferences 10-20 Deployment Process Preferences 10-21 Deploying Objects 10-22 Deploying Sequences 10-23 Control Center Jobs 10-24 OWB Automatically Creates a Connector 10-25 Loading the Target Warehouse 10-26 Course Progress Report 10-27 Executing Mappings 10-28 Executing the Process Flow 10-29 Execution Window 10-30 Course Progress Report 10-31 Viewing Data Using the Data Viewer 10-32 Practice 10-1: Deploying, Loading, and Viewing Data 10-33 Managing Metadata Using Dependency Manager 10-34 Integrated Lineage and Impact Analysis 10-35 Invoking Lineage and Impact Analysis 10-36 Lineage Analysis 10-37 Impact Analysis 10-38 Tree View 10-39 User-Defined Objects and Icons 10-40 Creating an Icon Set 10-41 Using an Icon Set 10-42 User-Defined Objects 10-43 Repository Browser 10-44

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


xiii

Starting the OWB Browser Listener 10-45 Logging In to the Warehouse Builder Browser 10-46 Browsing Design Repository Reports 10-47 Browsing Control Center Reports 10-48 Types of Control Center Reports 10-49 Object Summary Report 10-50 Execution Summary Report 10-51 Summary 10-52 Practice 10-2: Metadata Management 10-53

11 Business Intelligence Integration Objectives 11-2 Business Justification: Tools Integration 11-3 Integration with Discoverer 11-4 Two Ways to Define Discoverer Objects in Warehouse Builder 11-5 Creating a Business Definition Module 11-6 Creating a Business Area 11-7 Creating a Simple Item Folder 11-8 Creating a Drill Path 11-12 Deriving Individual Objects 11-13 Selecting Target and Rules for Derivation 11-14 Examining Derived Business Definitions 11-15 Deriving from a Collection 11-16 Creating a Complex Item Folder 11-18 Creating a List of Values 11-19 Creating Drill to Detail 11-20 Practice 11-1: Defining Business Intelligence Objects Based on Data Objects 11-21 Generating and Deploying the Intelligent Objects 11-22 Analyzing Data Using OracleBI Discoverer Components 11-23 Connecting to Discoverer Plus Relational 11-24 Examining EUL in Discoverer 11-25 Practice 11-2: Deploying OWB Business Intelligence Objects to a Discoverer End User Layer 11-27 Integration with BI Beans 11-28 Creating a Business Presentation Module 11-29 Creating a Presentation Template 11-30 Selecting the Report Type 11-31 Selecting the Items for the Report 11-32 Specifying the Report Layout 11-33 Connecting to the BI Beans Report Viewer 11-34 Examining the BI Beans Report 11-35

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


xiv

Drilling Down into the Report 11-36 Summary 11-37

Appendix A: Practices Appendix B: Practices Solutions Appendix C: MOLAP: Modeling and Loading Appendix D: Create the LOAD_SALES Mapping

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


Preface

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


Preface-3

ProfileBefore You Begin This CourseBefore you begin this course, you should have the following qualifications:Thorough knowledge of Oracle RDBMS, SQL DDL and DML, PL/SQL and database administration. You should be able to use a graphical user interface (GUI). The prerequisite is a familiarity with data processing concepts and techniques.Suggested PrerequisitesSuggested:

• Oracle Data Warehousing Fundamentals or equivalent Oracle computer based training course

• Technical understanding of information storage and retrieval within a database• Understanding of data warehouse architecture, including multi-dimensional models• Understanding of data warehouse development methodology• Database Design for Oracle Warehouses course• Oracle University eStudy: Introduction to Business Intelligence Products• OTN Oracle By Example (OBE): Introduction to Oracle Warehouse Builder 10g Release 2

Follow-up Courses• Oracle University ILT: Oracle Warehouse Builder 10g: Implementation Part 2 D18396GC10

• Oracle University 2-day ILT: Oracle 10g: Using OLAP• Oracle University 2-day ILT: Administration

How This Course Is OrganizedOracle Warehouse Builder 10g: Implementation Part 1 is an instructor-led course featuring lectures and hands-on exercises. Instructor demonstrations and practice sessions reinforce the concepts and skills that are introduced.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


Preface-4

Related PublicationsOracle Publications

Title Part Number

Oracle Warehouse Builder Online Documentation Library B31080-01Additional Publications

• Warehouse Builder Product Management OTN websitehttp://www.oracle.com/technology/products/warehouse/index.html

• System release bulletins• Installation and user’s guides• read.me files• International Oracle User’s Group (IOUG) articles• Oracle Magazine

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


Preface-5

Typographic ConventionsWhat follows are two lists of typographical conventions that are used specifically within text or within code.

Typographic Conventions Within TextConvention Object or Term Example

Uppercase Commands, Use the SELECT command to viewfunctions, information stored in the LAST_NAMEcolumn names, column of the EMPLOYEES table.table names,PL/SQL objects,schemas

Lowercase, Filenames, where: role is the name of the role italic syntax variables, to be created.

usernames,passwords

Initial cap Trigger and Assign a When-Validate-Item trigger tobutton names the ORD block.

Choose Cancel.

Italic Books, names of For more information on the subject seecourses and Oracle SQL Referencemanuals, and Manualemphasized words or phrases Do not save changes to the database.

Quotation marks Lesson module This subject is covered in Lesson 3,titles referenced “Working with Objects.”within a course

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


Preface-6

Typographic Conventions (continued)

Typographic Conventions Within CodeConvention Object or Term Example

Uppercase Commands, SELECT employee_idfunctions FROM employees;

Lowercase, Syntax variables CREATE ROLE role;italic

Initial cap Forms triggers Form module: ORDTrigger level: S_ITEM.QUANTITYitemTrigger name: When-Validate-Item. . .

Lowercase Column names, . . .table names, OG_ACTIVATE_LAYERfilenames, (OG_GET_LAYER ('prod_pie_layer'))PL/SQL objects . . .

SELECT last_nameFROM employees;

Bold Text that must CREATE USER scottbe entered by a IDENTIFIED BY tiger;user

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y



Introduction

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


Oracle Warehouse Builder 10g: Implementation Part 1 I-2


Lesson Objectives

After completing this lesson, you should be able to do the following:• Identify the objectives of this course• Discuss the course agenda and topics

You also become familiar with the backgrounds of your classmates.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Course Objectives

After completing this course, you should be able to perform the critical-path activities involved in creating and maintaining a data warehouse, including:• Defining sources• Designing the target warehouse• Defining source-to-target mappings• Extracting, transforming, and loading data into

staging tables and an enterprise model warehouse• Generating and deploying OWB scripts to create

warehouse database objects• Designing, creating, and populating dependent

data marts

Course ObjectivesThis course covers the critical-path activities for creating a data warehouse with Oracle Warehouse Builder (OWB). The fundamental tasks in data warehouse development are designing, building, and extracting. Using Oracle Warehouse Builder, the instructors guide you through the development of a data warehouse.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Agenda: Day 1

Lesson I: IntroductionLesson 1: Setting Up and Starting Warehouse BuilderLesson 2: Introducing OWB 10g R2 Architecture and

ConfigurationLesson 3: Defining Source MetadataLesson 4: Ensuring Data Quality Using Data ProfilingLesson 5: Defining Staging Metadata and Mapping

Tables

Agenda: Day 1Lesson I (this lesson) covers the objectives and the agenda of the course.Lesson 1 describes the Oracle Warehouse Builder program group components and introduces the typical classroom stand-alone setup.Lesson 2 provides an understanding of the Oracle Warehouse Builder architecture and configuration.In Lesson 3, you begin with the first task in building an Oracle Warehouse Builder data warehouse: defining data sources. You learn how to use Oracle Warehouse Builder wizards to create source modules and import metadata into them.In Lesson 4, you use Oracle Warehouse Builder data profiling features to maintain the quality of both your data and metadata.In Lesson 5, you create a staging area. The staging area is an area where data is temporarily stored and acts as a working area for extract, transform, and load (ETL) processing.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Agenda: Day 2

Lesson 5: Defining Staging Metadata and MappingTables (continued)

Lesson 6: Deriving Data Rules and Running Correction Mappings

Lesson 7: Defining a Relational Dimensional ModelLesson 8: Handling Slowly Changing Dimensions

Agenda: Day 2After profiling data in Lesson 4, you learn in Lesson 6 about how to derive data rules and run correction mappings. Lesson 7 aims at building the relational target warehouse. In this lesson, you model relational objects, dimensions, and a cube to form a basis for a relational star schema. You also learn how to create Oracle Warehouse Builder mappings to build an ETL solution and use the new features of the mapping editor.Lesson 8 provides an understanding about how to use Oracle Warehouse Builder to define, deploy, and load the three types of Slowly Changing Dimensions (SCDs).

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Agenda: Day 3

Lesson 9: Using Process FlowsLesson 10: Deploying, Loading, and Viewing DataLesson 11: Business Intelligence Integration

Agenda: Day 3In Lesson 9, you learn how to create and define process flows that interrelate mappings and activities external to Oracle Warehouse Builder.Lesson 10 aims to see the results of your hard work. In this lesson, you learn how to deploy and create the physical instance of your target.Lesson 11 aims at performing ad hoc queries on top of the relational data warehouse. You learn how Oracle Warehouse Builder integrates seamlessly with Oracle’s ad hoc reporting tool, Oracle Business Intelligence Discoverer.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Appendixes

Appendix A: PracticesAppendix B: Practice SolutionsAppendix C: MOLAP: Modeling and LoadingAppendix D: Create the LOAD_SALES Mapping

AppendixesAppendix A: Practices: This appendix contains the practices for this course.Appendix B: Practice Solutions: This appendix contains solutions for all the practices.Appendix C: MOLAP: Modeling and Loading: This is a lecture-only introduction to Oracle Warehouse Builder OLAP (online analytical processing) capabilities. The hands-on experience using OLAP is covered in the lesson titled “Understanding Oracle OLAP Concepts and Technology” of the Oracle Warehouse Builder 10g: Implementation Part 2 course.Appendix D: Create the LOAD_SALES Mapping: This appendix lists all the steps to design the LOAD_SALES mapping. This mapping, when deployed and executed, will load data into the SALES cube.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Questions About You

To ensure that the class can be customized to your specific needs and to encourage dialogue among all, answer the following questions:• Which organization do you work for?• What is your role in your organization?• What is your level of data warehousing expertise?• What do you hope to get out of this class?

Questions About YouYou get much more out of this class if you know the backgrounds of your classmates and the issues that they face in the development of a data warehouse. Each student has a unique perspective, experience, and knowledge from which you all can learn.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Summary

In this lesson, you should have learned about the course agenda.You should also have become familiar with the backgrounds of your classmates.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y



Setting Up and Starting Warehouse Builder

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


Oracle Warehouse Builder 10g: Implementation Part 1 1-2


Objectives

After completing this lesson, you should be able to do the following:• Describe typical Oracle Warehouse Builder

configurations, including the classroom stand-alone setup

• Describe Oracle Warehouse Builder program group components

• Log in to the Design Center• Create a design repository and users• Open a project and navigate the user interface

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




What Is Oracle Warehouse Builder?

Oracle Warehouse Builder (OWB) is an extensible framework for designing, deploying, and managing enterprise data warehouses, data marts, and e-business intelligence applications.

What Is Oracle Warehouse Builder?Oracle Warehouse Builder, also known as Warehouse Builder or OWB, is a business intelligence tool that provides an integrated solution for designing and deploying enterprise data warehouses, data marts, and business intelligence applications. Warehouse Builder is more than an extract, transform, and load (ETL) tool. It supports the complete data warehouse life cycle:

• Design: Importing enterprise data models, graphical modeling of multidimensional schemas, and intuitive mapping of the source to the target

• Build: Generation and population of the warehouse and marts by using Oracle database features

• Extract, transform, and load data: Extracting relational sources, flat file sources, and enterprise resource planning (ERP) sources, such as Oracle E-Business Suite, PeopleSoft, and SAP

• Integrate: Integrating readily with the Oracle database (Oracle Real Application Clusters, Oracle Online Analytical Processing, Oracle Spatial, Oracle Enterprise Manager, and so on), Oracle E-Business Suite, and Oracle Business Intelligence Discoverer

• Maintain: Maintaining the warehouse and refreshing data

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Producing Quality Information

Warehouse Builder enables the extraction, transformation, and loading of data to produce quality information in the Oracle database.

Data Information Knowledge

TransformationBusiness

intelligence Action

(Qualityinformation)

Producing Quality InformationInformation gathered in a data warehouse is useful only if it is of dependable quality and is delivered at the right time. As an information provider or integrator, you need a toolset that you can use to create quality information. Warehouse Builder forms a crucial part of that toolset. The core capability of Warehouse Builder is to deliver quality information at the right time to the analytic user.After data has been transformed into this quality information, Warehouse Builder enables the analysis of the business intelligence (BI) environment needed to transform this information into knowledge. Now the organization is in charge of its environment and applies this knowledge to business opportunities and problems to receive the benefits.Warehouse Builder has many features that you can use to create quality information. The following are some of the features:

• Data profiling• Match-merge• Name and address cleansing• Metadata quality through dependency management, impact, and lineage diagrams• Business intelligence modeling

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




New Segmentation of OWB FunctionalityEnterprise ETL Option

Enable large-scale,complex deployments

Data Quality Option

Convert data to quality Information on an ongoing basis:• Data profiling• Derivation of rules• Correction maps

Connectors

Extract from commonERP/CRM:• SAP• PeopleSoft 8/9• Oracle E-Business

Suite

Core ETL FeaturesEasily load data into the Oracle database:

• Bundled with Database SE1/SE/EE at no extra charge• Packaged as a separate media pack• Includes all existing 10g R1 functionality, plus “experts”

Note: Options and connectors are available for licensing with Oracle Database Enterprise Edition only.

New Segmentation of OWB FunctionalityCore ETL FeaturesThe aim of the Core ETL features is to provide core bulk ETL functionality as part of the database license. Common and repetitive tasks can be fully automated using public APIs and extensions (new scripting macros called “experts”). These features enable Oracle database customers to quickly and easily load data into an Oracle database. Core ETL features include all existing Oracle Database 10g Release 1 functionalities as well as “experts.”Enterprise ETL OptionThe aim of the Enterprise ETL Option is to support large-scale and complex deployments by improving the scalability and performance of ETL jobs. Support is also provided to effectively manage multienvironment deployments that are typical of enterprise data warehouse projects. Some examples of this option’s functionality are:

• Improved performance and scalability of ETL jobs• Transportable tablespaces• Data Pump• Support for large global enterprisewide deployments• Interactive lineage and impact analysis• User-defined objects

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




New Segmentation of OWB FunctionalityEnterprise ETL Option

Enable large-scale,complex deployments

Data Quality Option

Convert data to quality information on an ongoing basis:• Data profiling• Derivation of rules• Correction maps

Connectors

Extract from commonERP/CRM:• SAP• PeopleSoft 8/9• Oracle E-Business

Suite

Core ETL FeaturesEasily load data into the Oracle database:

• Bundled with Database SE1/SE/EE at no extra charge• Packaged as a separate media pack• Includes all existing 10g R1 functionality, plus “experts”

Note: Options and connectors are available for licensingwith Oracle Database Enterprise Edition only.

New Segmentation of OWB Functionality (continued)Data Quality OptionThe aim of the Data Quality Option is to support the transformation of data into quality information on an ongoing basis. This option contains the following functionalities:

• Discover data anomalies• Identify and create data rules• Autocorrect data anomalies• Audit ETL jobs (and take action if data quality is too low)

ConnectorsConnectors enable customers to quickly and easily extract data from (and in some cases target data to) their CRM (customer relationship management) and ERP (enterprise resource planning) applications. The following connectors are available:

• SAP• Oracle E-Business Suite• PeopleSoft 8/9

For example, if a customer has three Oracle E-Business Suite sources and the target is a single Oracle database, only one connector would need to be purchased. If there are two target Oracle databases, two connectors would need to be purchased.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




BI Environment from an OWB Perspective

Model, extract, transform, load, and manage BI data

Create analyticcontent

Share BusinessIntelligence

Reports

BI Beans Disco Plus

Spread-sheet add-in

Portal page

Disco Viewer

BI Beans application

• Relational• Flat files• Applications• Mainframe• SAP

Sources

Tools using BI data

Relational

Multi-dimensional

(OLAP)

OWBrepository

and/or

Oracle database

OWB

BI Environment from an OWB PerspectiveBefore you can use BI tools and applications, someone must acquire and prepare data.DesignWarehouse Builder is a tool that you can use to design a business intelligence system. The paradigm throughout the product is that you import definitions, define target structures, validate the structures, generate the code to implement the structures, and deploy the mappings to the target environment. MaintainAfter the mappings are deployed, Warehouse Builder assists in the daily maintenance as well as the monitoring of the deployed system. Leverage Oracle Database InvestmentsThroughout the product, leveraging of Oracle database investments, as well as integration with other Oracle tools, is important.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




OWB Sources and Targets

Applications: Oracle Applications, PeopleSoft, Custom SQL applications, and so on

Applications: Oracle Applications, SAP, PeopleSoft, Custom SQL applications, and so on

Flat filesFlat files

ODBCODBC

Other vendors: IBM DB2, Microsoft SQL Server, Sybase, Informix, Mainframes, and so on (via Oracle Transparent Gateways)

Other vendors: IBM DB2, Microsoft SQL Server, Sybase, Informix, Mainframes, and so on (via Oracle Transparent Gateways)

Oracle:Tables, views, materialized views, external tables, dimensions, cubes, and so on

Oracle: Tables, views, materialized views, external tables, transportable tablespaces, SQL*Loader, and so on

TargetsSources

OWB Sources and TargetsThis table shows various sources and targets supported by Oracle Warehouse Builder 10gRelease 2.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Installing OWB

Read the entire installation document before:• Choosing a configuration environment• Choosing the order of installation• Starting the installation

Oracle Warehouse Builder Installation and Configuration Guide

Installing OWBFirst Step: Study the DocumentationBy previewing the Oracle Warehouse Builder Installation and Configuration Guide, you can make informed decisions on issues such as:

• Three-tier versus two-tier configuration• Hardware, software, disk space, and memory requirements• Order of installation

Note: This section about installation is not intended to be a substitute for the installation document, but rather a complement to the documentation. Use the documentation as the primary source of detailed installation procedures and information.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Hardware and Software Requirements

• Hardware requirements for Microsoft Windows:– 963 MB disk space for OWB installation– 1 GB memory– 1 GB page file size, TMP, or swap space– 1 GHz Pentium processor or equivalent

• Software requirements: Supported operating systems:– Microsoft Windows XP– Microsoft Windows 2000– Windows Server 2003– Linux x86 (Red Hat Enterprise Linux AS/ES, SLES,

and Asianux, and SuSE LINUX Enterprise Server)– HP-UX PA-RISC– IBM AIX

Hardware and Software RequirementsThe guidelines that are given in the slide are the minimum requirements. Memory requirements may increase, depending on the functions being performed, the number of users connected, and the size of your data warehouse or marts.You must also ensure that you have ample swap space.Supported Operating SystemsOracle Warehouse Builder 10g Release 2 is available on Windows (32-bit), Linux (x86), HP-UX PA-RISC, and IBM AIX platforms. Note that the user interface (Design Center) is supported only on Windows and Linux; other platforms (HP-UX PA-RISC and IBM AIX) are supported as run-time environments only (Control Center). Location of DatabaseYou must have the Oracle database installed on the same computer where you plan to install your Warehouse Builder repository. Oracle Home DirectoriesInstall Warehouse Builder in a separate, new Oracle home directory. Do not install any other products in this directory.db_block_size Settings

• For the machine hosting the data warehouse, use db_block_size of 16 k or larger, depending on the installation.

• For the machine hosting the OWB repository, use db_block_size of 4 k or 8 k.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Supported and Certified Versionsof Oracle RDBMS

• Oracle Database 10g or Oracle9i Database (9.2) Enterprise Edition is installed on computers hosting the Warehouse Builder repository and targets.

• Deploying dimensional structures to an analytic workspace requires either Oracle Database 10gRelease 2 or Oracle Database 10g Release 1 (10.1.0.3) with the 10.1.0.4 patch set, with the OLAP option selected.

• RDBMS support for data warehousing includes:– Oracle Enterprise Manager (OEM) integration for the

“warehouse upgrade” feature and job scheduling– Oracle Workflow for dependency management– The MERGE command– Full outer joins, and much more

Supported and Certified Versions of Oracle RDBMSOracle Warehouse Builder requires the Enterprise Edition version of the Oracle database. Oracle Warehouse Builder 10g Release 2 is supported on Oracle Database 10g Release 2 for both the repository and the target.Note: Starting with Oracle Warehouse Builder 10g Release 2, the Standard Edition of the Oracle database is supported on both the repository and the target. However, the Standard Edition does not support the partitioning, bitmap indexing, and business intelligence features, which are supported only by the Enterprise Edition.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Software Versions Compatiblewith Warehouse Builder

• Supported Oracle database versions:– Sources: 8.1.7, 9.0.x, 9.2.x, 10g Releases 1 and 2– Targets: 9.2.x, 10g Releases 1 and 2– OWB Repository: 9.2.x, 10g Releases 1 and 2– Oracle OLAP: 10.1.0.4 and later

• Discoverer: 10g• BI Beans: 10g• SAP: 3.x, 4.x• Oracle Enterprise Manager: 9.0.x, 9.2.x• Oracle Workflow: 2.6.2, 2.6.3, 2.6.4 (OWF 10g)• Oracle Applications (Concurrent Manager): 11i

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




OWB Product Components

• Design Center• OMB Plus• Repository Browser• Administration • Repository Assistant:

– Start or Stop Control Center Service– Start or Stop OWB Browser Listener

OWB Product ComponentsThis slide shows the range of components that make up the OWB product.

Administration

Repository Assistant Facility for creating and managing OWB repositories and users

Start or Stop Control Center Service

Facilities for starting and stopping the OWB Control Center Service

Start or Stop OWB Browser Listener

Facilities for starting and stopping the Repository Browser Listener for stand-alone local browser (OC4J)

Design Center The main OWB client in which you design sources, targets, ETL mapping transformations, and so on

OMB Plus The scripting tool you use to execute tcl scripts Repository Browser

The reporting environment for examining repository metadata in a read-only manner. (In the production release, invoking the Repository Browser automatically starts the listener if it is not already running.)

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Installing and Configuring OWB

Run the Oracle Universal Installerto install the OWB software.

Create target schemas.

Start the Design Center, and click the Get Started button. Or, select Administration > Repository Assistant to createusers.

You can create target schemas by using the Repository Assistant or by using the Security node in the Global Explorer panel in the Design Center.

Installing and Configuring OWBThis flowchart illustrates the high-level installation steps. For more details about setting up a Warehouse Builder environment, see the OWB release notes and the installation guide. Installation Notes

• Although Oracle Workflow Runtime components are still required for a complete Warehouse Builder installation, the role of Oracle Workflow Client has been replaced with the Warehouse Builder Process Editor.

• There is no need to install the Warehouse Builder Workflow Queue Listener. The Workflow Queue Listener has been replaced with the Runtime Platform Service.

• The Repository Browser can run as a stand-alone client without application server, using local OC4J (Oracle Application Server Containers for J2EE) containers. You still have the option to install a multiuser version of this browser integrated with Oracle Application Server 10g.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Configuring OWB

• Warehouse Builder:- Design Center- Repository Assistant- Repository Browser- Control Center Service- OMB Plus scripting

• Net client• Web browser• OEM client (O)• Workflow client (O)

• Oracle database• Oracle Agent• TNS listener• Oracle Management Service (OMS)• Oracle Application Server 10g: HTTP

Server and Portal (O)• Workflow Monitor• OWB Runtime Platform Service• Database object for:

OWB : Repository schema: Target schema

Portal (O)Workflow Server (O)OEM repository (O)

Client Database

O = optional

Configuring OWBWarehouse Builder always runs in a two-tier client/server mode, with the Warehouse Builder “thick” client pointing to a database machine. Warehouse Builder connects to the database to get the metadata and also to deploy objects and execute scripts.Possible Three-Tier ConfigurationThe only product components that can possibly serve in three-tier mode are those that run on Oracle Application Server 10g (multiple-user reporting via Portal, Oracle Workflow, and Oracle Enterprise Manager) as a pseudo–middle tier. In a two-tier environment, the middle tier and database tier reside on the same machine. You must decide on your configuration before proceeding with the OWB installation.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Classroom Stand-alone ConfigurationEach

student PCThe following reside on each computer:– Source flat files and schemas– Metadata repository– Target schema– All data warehousing software

• Warehouse Builder:- Design Center- Repository Assistant- Repository Browser- Control Center Service- OMB Plus scripting

• Oracle Database 10g:- Repository schema- Source and target schemas

• Workflow Server• OracleBI 10g components (Discoverer for OLAP to show integration)

Classroom Stand-alone ConfigurationIn this classroom environment, all the software resides on the same machine. The classroom environment does not represent a typical production environment because the following reside on the same computer:

• Source flat files and schemas• Metadata repository• Target schema• All data warehousing software

Installation Log File• The installation log file is located in:

<OWB HOME>\owb\UnifiedRepos• Log file naming convention: log.000.log, log.001.log, and so on

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




OWB 10g R2 Default Installationwith a Single Repository

Repository user

Repository ownerHighly privilegeddatabase user Create database

objects:- Tables- Dimensions, cubes - Mappings- Packages, …

Target schemas

Repository users Repository owner Target users

Created by the OWB Repository Assistantor

Logon dialog box’s Get Started button

Can be a single repository

Created by therepository owner

- Audit tables- Run-time and

deployment statistics- Physical location info

- Design metadata- Possible target

OWB 10g R2 Default Installation with a Single RepositoryIn Oracle Warehouse Builder 10g Release 2, the default installation creates a single repository in a single database schema. This repository or schema (called repository owner) plays the role of both design and run-time repositories when compared to that in Oracle Warehouse Builder 10g Release 1. In the default installation, the repository owner is a highly privileged database user. This repository owner cannot be a target schema.OWB Repository Owner and OWB Repository UsersThere is an OWB repository owner and one or more OWB repository users that can access the repository. Those users may be targets, but can also be used to control access to the OWB repository.Remote DeploymentIf you install a remote repository, you must ensure that you have a local control center service running.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Target Users

Repository user

Repository ownerHighly privilegeddatabase user Create database

objects:- Tables- Dimensions, cubes - Mappings- Packages, …

Target schemas

Repository users Repository owner Target users

Created by the OWB Repository Assistantor

Logon dialog box’s Get Started button

Can be a single repository



- Design metadata- Possible target

Created by therepository owner

Target UsersA target user is the schema in which you deploy your objects, such as tables and mappings. You must register a target user with a repository in order for it to accept deployment actions. You can do this registration either when installing a repository or within a design session, using a user that has Warehouse Builder administration privileges.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Logging In to OWB Design Center

You can initially use the Get Started button to create a user, after which you should use privileged users in the Design Center to administer other users.

Logging In to OWB Design CenterLogging in to Oracle Warehouse Builder connects you to the Oracle Warehouse Builder Design Repository database where your warehouse design metadata is stored.

1. Select Start > Programs > Oracle – OwbHome10gR2 > Warehouse Builder > Design Center.

2. Enter the username and password of an OWB user if you defined them earlier using Repository Assistant, or click Get Started to create the first user now. Before logging in, you must establish the login credentials. Click Show Details. Provide the host name, port number, and Oracle service name that were defined during the Oracle database installation. Click OK. The main OWB console appears.

Where to StartA project is the highest-level object in OWB. (When you first install OWB, there is only the project named “MY_PROJECT”; in the prepopulated class repository, several projects are listed.) Expand the MY_PROJECT node. Normally, it is not recommended that you start your work in this default project.Selecting a ProjectAll object definitions that are created during your work session are stored in the Oracle Warehouse Builder repository and are organized within projects. Projects are discussed in detail later in this lesson.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 1-1:Creating a Repository Owner and User

This practice covers the following topics:• Invoking the Warehouse Builder Design Center

Logon dialog box• Creating a repository user and repository owner

Practice 1-1: Creating a Repository User and OwnerIn this practice, you invoke the Warehouse Builder Design Center dialog box. Using the Logon page, you create a repository user and repository owner. Later, you create a target user.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Projects

• A project is the highest-level object in Warehouse Builder.

• It is best to create projects after identifying the functional areas for the projects.

Source module

Mapping

Transformations

Mapping

Transformations

Warehousemodule

Warehousemodule

Project A

Project B

Warehousemodule

Staging

Operational data sources Data Mart

ProjectsAll work to build a warehouse is performed within the context of a project. A finished project contains metadata and definitions for objects that are needed to build a warehouse:

• Database modules• File modules

Within these modules, you define:• Tables and views• Sequences• Dimensions and cubes• Materialized views• Mappings• Transformations• Function categories (packages, PL/SQL functions, and procedures)• Process flows, schedules, profiles, and so on

By using projects, you can organize your work for a specific goal.Note: The class case study used in all practices uses a single project to contain all source and target modules.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Organizing Your Work in Projects

Warehouse module

MappingsTransformations

Cube table DimensionsMaterialized views

WarehouseWarehouse module


Tables ViewsSequences Temp tables

Warehouse module


Tables ViewsSequences Temp tables

SourceWarehouse module

Tables ViewsSequences Flat filesCustom schema objects

Warehouse to Data Mart Project

Source to Warehouse Project

Data mart

Warehouse

Organizing Your Work in ProjectsYou can create projects according to functional areas. For example, you can build a sales project that would create a data warehouse for the sales aspect of your business.Within projects, use modules to specialize your metadata for the functional purpose (for example, a module for the staging area, one for the operational data store, and one per data mart).For phasing your work, you learn how to use a combination of:

• Snapshots• Multiple named configurations

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Concurrent Users per Projectwith Object Locking

A database can contain multiple users’ OWB repositories.Multiple users can work on the same project.

Jan

Trevor

Project 1

Project 2

Database

Repository B

Repository AKim

Project 1

Concurrent Users per Project with Object LockingMultiple Users per ProjectMultiple users can concurrently access an OWB project. OWB uses a locking mechanism to control concurrent user access to metadata objects. The locking mechanism is explained in detail in the next slide.Multiple Projects per OWB RepositoryEach OWB repository, which is accessed by using a user ID and password login, can store multiple OWB projects.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Multiple User AccessTitle bar indicates

read/write orread-only mode.

An attempt to open an object already opened and locked by another user results in a warning, allowing read-only access.

An attempt to delete a read-only object

locked by another user results in a warning.

Multiple User Access Locking MechanismOWB features a locking mechanism that ensures that only one user has write privileges to a particular object while simultaneously enabling other users to maintain read-only privileges to that object.Duration of LockThe lock is maintained for the duration of any transaction that is started by the write-privileged user. The lock is released when the user commits the changes or performs a rollback and closes all editors that are associated with the object.OWB employs a user interface–based lock. If you commit your work but keep the editor open, the lock is not released. You must close the editor and commit for the lock to be released.If you open a table in the Data Object Editor, OWB locks the metadata definition of the table’s attributes.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Design Center

ToolbarMenus

Connection explorer

Global explorer

Project explorer

Project explorer: Holds all information related to a single projectConnection explorer: Holds all connections and control centers for the repositoryGlobal explorer: Holds all objects that are shared among users of the repository; this is a great place to share reusable components across projects

Design CenterWhen you log in to OWB, the Design Center window shows the projects that are available to your login user repository. The empty default project from installation is MY_PROJECT.ExplorersThe Design Center is divided into Project, Connection, and Global explorer panels.Save All and Revert to SavedIt is essential that you periodically select Save All from the Design menu to avoid losing potentially large amounts of work. While working, you can choose Revert to Saved, which returns you to the previous save point.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Objects Within a Project

Oraclemodules

Objects Within a ProjectThe Project navigator tree displays all objects currently defined for the project. The highest-level objects (databases, files, and so on) are types of modules organizing the tree in a common way.DatabasesDatabases represent general database applications, which can be both Oracle databases and non-Oracle databases.ModulesA module is a logical grouping of several object definitions. Modules appear under many of the highest-level nodes on the navigator tree. However, modules are not grouped under a node named “Modules” on the tree.For example, an Oracle database module would be a logical grouping of objects that belong to an Oracle database schema. This slide shows two Oracle database modules: SALES_WHand XSALES.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y





Files

Applications

Objects Within a Project (continued)The Project navigator tree displays all objects that are currently defined for the project.FilesA file definition represents a “connection” to a folder that contains source flat files. You can use wizards to sample the flat files. ApplicationsAn application definition represents a database connection to one of the following source applications:

• Oracle E-Business Suite• PeopleSoft 8 or 9• SAP R/3 3.x or 4.x

Data ProfilesIn the lesson titled “Ensuring Data Quality Using Data Profiling,” you use the Data Profile Editor to discover patterns, relationships, redundancies, and dependencies among tables, views, dimensions, and facts.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y





Pluggable mappings

Process flow modules

Process flow

Data rules

Objects Within a Project (continued)Data RulesA data rule is an expression ensuring that only valid values are stored within a data object. Data rules can also establish the set of legal relationships that can exist between data objects. These rules can be derived from the results of data profiling or they can be defined manually. Data rules can be applied to tables, external tables, views, and materialized views.Pluggable MappingsPluggable mappings increase design productivity through reusable logic that you can incorporate into various ETL processes or share among many designers. After you create a mapping, you can create a pluggable mapping around the portion of the flow you want to reuse. A pluggable mapping is a reusable grouping of mapping operators that can be nested in another mapping as a single operator. Process FlowsYou can define and execute process flows that manage dependencies among mappings and other activities internal and external to Warehouse Builder (such as e-mail, FTP commands, and operating system executables). For example, you can design a process flow such that the completion of one mapping triggers an e-mail notification and launches another mapping.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y





User-defined modulesfor user-defined objectscreated via OMB Plus scripting

Schedules

Derived object for OracleBI Discoverer

Derived object for OracleBI Beans

Objects Within a Project (continued)SchedulesYou can create schedules to plan when and how often to execute mappings, process flows, transformations, data profiles, and data auditors. Schedules are deployed to schedulers such as the Oracle Database 10g scheduler.Business IntelligenceYou can derive business intelligence objects from your repository definitions and plug them directly into business intelligence (BI) systems such as Oracle Business Intelligence Discoverer and Oracle Business Intelligence Beans.User-Defined ModulesYou can use the Warehouse Builder OMB Plus scripting language to define user-defined objects (UDOs) for the repository in addition to existing Warehouse Builder objects. After you create a UDO via scripting, Warehouse Builder displays the custom object in the Project Explorer under the User Defined Modules node.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y





Experts

Collections

Named configurationsfor multiple targets

Objects Within a Project (continued)ExpertsConceptually similar to macros, experts are graphical taskflows of OWB user interface components, aimed toward accomplishing a goal or task. For example, you can build a Data Mover expert as an easy and interactive method for less-experienced users to load data. ConfigurationsWith Warehouse Builder, you can define multiple named configurations for the same set of objects. Use this if you are deploying the same system into multiple environments, such as test and production. Each project comes with a default configuration. If you define multiple configurations, then you assign one as the project’s active configuration, which is shown in the status bar. Each configuration has an associated control center, which ensures that dimensional objects, mappings, and so on are deployed to the correct environment.CollectionsCollections represent a generic grouping mechanism. You can use a collection to hold shortcuts to several object definitions; you can then use the collection to perform a group activity such as validation, code generation, or metadata export.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Objects Within a Module

Tables

Dimensions

Cubes

Module node expanded to show its objects

Objects Within a ModuleDimensionsDimensions may consist of one or more levels and hierarchies, and contain attributes. For deployment to a relational implementation in an Oracle database, Warehouse Builder generates the dimension object. For an OLAP (online analytical processing) environment, the entire dimension definition is created as an OLAP structure and registered in the Oracle database analytic workspace. CubesCubes are described by dimensions. As such, cubes are a part of dimensional modeling. Typically, a cube has relationships to one or more dimensions and contains measures of the data that you are interested in. TablesYou often use relational table definitions in the design of a business intelligence system (for example, to define the relational tables that load data into dimensions).

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y





External tables

Views

Materialized views

Sequences

Objects Within a Module (continued)External TablesYou can define an external table as an alternative to a flat file as a source definition in a mapping. (Flat files require SQL*Loader to load the data.) Some advantages of the external table definition compared with a flat file definition include:

• Running selects in parallel• Flexibility in PL/SQL-based transformations because of the heterogeneous join

capability between external tables and relational tablesThe latter advantage may eliminate an additional staging step that would have been necessary if you were using SQL*Loader to load the data.Views and Materialized ViewsYou may want to include view definitions to simplify eventual query retrieval from your target system. In a business intelligence environment, materialized (populated) views may be very important to speed up eventual query retrieval. SequencesSequence definitions can be used as a source object definition on a mapping to generate a numeric sequence value.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y





Data auditors

Transformations

Mappings

Objects Within a Module (continued)As mentioned earlier in the lesson, a module is a logical grouping of several object definitions. The following objects can be defined within a database target module:MappingsMappings model the flow of data from the source to the target, including any ETL process. TransformationsTransformations implement any user-defined PL/SQL code that is implemented as a function, procedure, or package. Warehouse Builder provides the flexibility for you to define any PL/SQL code and include it in a mapping to implement any transformation. Data AuditorsData auditors are processes that validate data against a set of data rules to determine which records comply and which do not. They can be added to a process flow and can be scheduled.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y





Queues

User-defined types

Objects Within a Module (continued)User-Defined TypesIn addition to the standard object types provided by Warehouse Builder, you can define custom object, varray, and nested table types. With user-defined types, you can define complex data type definitions to use in your applications. For example, you can encapsulate a customer address definition in a special type.QueuesQueues can be used both as a source and as a target on a mapping. When used as a source, Warehouse Builder generates code to extract all appropriate messages and run these in highly performing set-based mode. Advanced queues enable message management and communication required for application integration.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Locations, Connectors,and Control Centers

Connectors

Oracle database locations

Control centers

Files locations

Workflow location

Discoverer location

Locations, Connectors, and Control CentersThe Connection Explorer lists locations and control centers shared across the repository.LocationsA location is a physical place in the run-time environment holding schema and database information. The location is related to a module determining what the physical location will be for the metadata in the module. For easy access, locations are organized into types of locations, such as database locations, files locations, Workflow (process flow engine) locations, and Discoverer locations. ConnectorsConnectors define a path to go from one location (source) to another location (target) and are owned by the target location. So if you need data from the HR schema in the database and from the SH schema in the database, the connector is the link from SH to HR to select data from the two schemas.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Locations, Connectors,and Control Centers

Connectors

Oracle database locations

Control centers

Files locations

Workflow location

Discoverer location

Locations, Connectors, and Control Centers (continued)Control CentersA control center is a central graphical facility that enables you to view and manage all aspects of objects. You can define multiple local and remote control centers, which are linked to your project via the named configuration. For example, if you choose DEFAULT_CONFIGURATION, the associated control center is DEFAULT_CONTROL_CENTER. Changing the configuration, therefore, changes the control center you deploy objects to.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Global Explorer Objects

Security node seenonly by users grantedthe Administrator role

Global Explorer ObjectsThe Global Explorer panel lists a variety of objects shared among projects in the repository:

• Public transformations• Public experts• Public user-defined modules• Public data rules• Icon sets• Security

Using the security graphical interface, administrators can grant object and system privileges to users. The security node is visible only to users with the Administrator role.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating a Project

Creating a ProjectYou can create a project by selecting New from the Design menu, provided the cursor is on the Project Explorer or on any of the project names.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Setting Project Preferences

Setting Project PreferencesWarehouse Builder enables you to set preferences such as locale appearance, deployment processing preferences, environment behaviors, logging file and message settings, naming behavior, and security parameters.To set preferences, select Preferences from the Tools menu.Appearance PreferencesYou can set locale-specific language settings, such as Chinese, Hong Kong; Chinese,Taiwan; or Chinese, China.Process Deployment PreferencesYou can specify a number of processing preferences such as allowing undo/redo operations, pausing after compilation, and showing various prompts and messages.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Setting Project Preferences

Setting Project Preferences (continued)Environment PreferencesYou can specify a variety of environment preferences. For example, you can hide the initial welcome page for all wizards. You can control various prompts when objects are deleted.Logging PreferencesYou can set log file options such as file path, file name, maximum size, and types of messages that are saved to the log file.Naming PreferencesYou can specify the use of physical names as used in generated code or more meaningful business names, and whether to propagate name changes from one mode to the other.Security ParametersThere are security parameters for use of passwords and for specifying user access privileges to metadata.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Summary

In this lesson, you should have learned how to:• Describe a variety of possible installation

configurations• Install Warehouse Builder• Create repository users and log in• Begin navigating through the Warehouse Builder

client user interface

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 1-2: Invoking OWBand Opening a Project

This practice covers the following topics:• Logging in to Warehouse Builder Design Center• Creating a new project• Viewing project properties• Navigating through the user interface

Practice 1-2: Invoking OWB and Opening a ProjectIn this practice, you invoke Warehouse Builder Design Center, log in as the user, open the existing project named “My Project,” create a new project, and examine the project’s properties.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y



Introducing OWB 10g R2 Architectureand Configuration

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Objectives

After completing this lesson, you should be able to do the following:• Discuss various design and run-time

configurations• Describe the Warehouse Builder repository

architecture, users, and owners• Explain the benefits of warehouse staging areas• Describe the course data sources and targets• Import metadata using tcl scripts

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Process Flow of Design and DeploymentDesign target object metadata.1

• Relational databases• Flat files• Applications• Mainframe• SAP

Map source to targetwith transformations.

3

Oracle 8i/9i/10g• OLAP• Flat files• BI tools• Non-Oracle

databasesvia gateways

Validate, generate, and deploy the code.4

5OWBrepository

OWBclient

Targetwarehouse

and data marts

Sources

Derive and deploy BI reportinginfrastructure.

Extract and transform data.6

7 Capture knowledge using “experts.”

Define A.Define B.Map A to B.

Extract sourcemetadata:

2

Process Flow of Design and DeploymentThe diagram in the slide illustrates the major steps in modeling, building, and populating a data warehouse.

1. Design target objects.Model the structure (metadata) of the target data warehouse objects.

2. Design sources and extract source metadata.Model the structure (metadata) of the source objects.

3. Map sources to targets.Model the mapping of data from the source objects to the target objects. Specify transformations to transform and clean the data.

4. Validate, generate, and deploy the code.Validate and generate scripts from your design. Deploy those scripts for building physical warehouse objects and extracting and transforming data.

5. Derive and deploy the BI Reporting Infrastructure for Discoverer and BI Beans.Oracle Warehouse Builder 10g Release 2 introduces object definitions that represent objects in the Oracle Business Intelligence Discoverer end-user layer. These can be designed (or derived, based on data object definitions) and then deployed to Discoverer.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Process Flow of Design and DeploymentDesign target object metadata.1

• Relational databases• Flat files• Applications• Mainframe• SAP

Map source to targetwith transformations.

3

Validate, generate,and deploy the code.4

5OWBrepository

OWBclient

Targetwarehouse

and data marts

Sources

Derive and deploy BI reportinginfrastructure.

Extract and transform data.6

7 Capture knowledge using “experts.”

Define A.Define B.Map A to B.

Extract sourcemetadata:

2

Oracle 8i/9i/10g• OLAP• Flat files• BI tools• Non-Oracle

databasesvia gateways

Process Flow of Design and Deployment (continued)5. Derive and deploy the BI Reporting Infrastructure for Discoverer and BI Beans.

(continued)Oracle Warehouse Builder 10g Release 2 introduces the ability to define skeleton cross-tab reports and graphs inside Oracle Warehouse Builder (called as Warehouse Builder or OWB). These definitions can be implemented as Oracle Business Intelligence Beans (BI Beans). The skeleton reports can be directly used by end users to look at data.

6. Extract and transform data.Deploy scripts to extract source data and load it into the warehouse or data mart. OWB supports the following targets: Oracle8i Database, Oracle9i Database, Oracle Database 10g, online analytical processing (OLAP), flat files, advanced queues, various Oracle Business Intelligence tools, and non-Oracle databases via gateways.

7. Capture knowledge with “experts.” You can create OWB experts to give directed guidance and promote best practices. An expert in Warehouse Builder implements a sequence of predefined tasks, managing the potential complexity faced by novice users. Experts are object definitions in Warehouse Builder that can be designed and executed. Experts can automate repetitive tasks and simplify tool interaction for novices.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




OWB 10g R2 Repository Default Installation

Highly privilegedrepository owner

Use the OWB Repository Assistant to create a repository, its owner, and its users.



Users associated with one repository

Repository users’possible job functions

- Metadata design- Deploying code- Executing code- Administrative tasks- Possible target schema

Repository users(schemas with usernames

in the database)

Repository owner(schema with username

in the database)

OWB 10g R2 Repository Default InstallationThe default installation provides a straightforward repository structure. The default installation creates a single repository that handles both design and run-time metadata. You use this setup to familiarize yourself with the basic concepts in the repository.OWB Repository Owner and OWB Repository UsersEach repository has one highly privileged repository owner and zero or more users associated with the repository. Some repository users may be assigned as warehouse targets for data undergoing extraction, transformation, and loading (ETL) processes. Other users may be used only to connect to Warehouse Builder or for setting metadata security and object ownership.Repository Owner and Users Created as Database SchemasOWB repository owners and users are created using new or existing Oracle database users. The OWB repository owner name and usernames are thus database schema usernames.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




OWB 10g R2 Repository: Design Phase


Repository users(database users withschema usernames)

Repository owner(database user withschema username)





- Metadata design- Deploying code - Executing code- Administrative tasks- Possible target schema

Items within red boxes are relevant to the design phase.

OWB 10g R2 Repository: Design PhaseThe diagram in the slide shows the possible job functions of the repository owner and users during the design phase.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




OWB Design Components

OWB Design Client

OWB Client User Schema

OWB Client User SchemaOWB client users

Code Generator

User-interface design editors

Repository owner

Design Center

RepositoryBrowser


OWB Client User SchemaTarget usersGenerated

code

Control Center Manager

Control Center Service

OWB Design ComponentsThe Warehouse Builder Design Center is the central design tool.User Interface: Design EditorsThe user interface provides several graphical editors for defining source and target metadata, as well as for the core ETL operations.Repository Browser The OWB Repository Browser enables you to view your design metadata from a Web-based application. The reports are based on data that is stored in the repository. The Repository Browser can run in a fully shared Oracle Application Server 10g environment. Alternatively, you can launch the Repository Browser locally as a stand-alone executable for single-user usage.(In a later phase, after you deploy your design objects to the database and execute OWB programs to populate the database, the Repository Browser also enables you to view deployment and execution audit information.)

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




OWB Design Components

OWB Design Client


OWB Client User SchemaOWB client users

RepositoryBrowser


OWB Client User SchemaTarget users

When multiple users work on a project, each person’s work is tracked and canbe traced.

Code Generator


Repository owner

Design Center

Generatedcode



OWB Design Components (continued)Repository Owner SchemaThe repository, installed in an Oracle database as a database user schema, stores the metadata definitions and run-time activities for all the objects in Warehouse Builder. You can access metadata that is stored here by using any of the following:

• The client user interface (read/write)• Oracle MetaBase (OMB) Plus (read/write), which is a flexible, command-line metadata

access tool for Warehouse Builder• SQL queries on public views (read-only)• Repository Browser (HTML, read-only)

OWB Client UsersThe person acting as an OWB user defines metadata representing sources, targets, and mappings. You can register any number of database users as OWB users. These users access the OWB repository under a security framework; the grants and privileges are managed by database roles. Users do not need all the system privileges that have been granted to the repository owner. Users may be assigned as targets.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




OWB 10g R2 Repository: Run Time


Repository usersRepository owner





- Metadata design- Deploying code- Executing code- Administrative tasks- Possible target schema

Items within red boxes are relevant to the run-time phase.

OWB 10g R2 Repository: Run TimeThe diagram in the slide shows the roles of the repository owner and users during the deployment and execution phases.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




OWB Run-Time Components

OWB Design Client


OWB Client User SchemaOWB client

user schemas

RepositoryBrowser


OWB Client User SchemaTarget

schemas

Code Generator


Repository ownerschema

Design Center

Generatedcode



OWB Run-Time ComponentsRuntime Repository is the infrastructure that OWB provides to manage the packages and objects that are generated from Warehouse Builder, the actual physical data, and the run-time metadata (load volumes, throughput, and so on) stored in the repository. Repository Owner SchemaThe repository owner schema contains all auditing tables and several audit API packages needed to manage the deployment and execution of objects. The repository owner requires significant system privileges to install and execute objects in another schema. The repository provides deployment, execution, auditing, and management. There is no need to define anything except the level of auditing that is required, and Warehouse Builder writes the necessary information to the repository. Another benefit is that the repository stores the entire deployment and execution history of your system. Code GeneratorThis component generates scripts (such as DDL and PL/SQL) based on the metadata in the repository. The generated scripts provide optimal performance for any Oracle database version. If you are running Oracle8i Database, Oracle9i Database, or Oracle Database 10g, your generated OWB code will use the newest features for these database releases.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




OWB Run-Time Components

OWB Design Client


OWB Client User SchemaOWB client

user schemas

Code Generator

User-interface design tools

Design Center

RepositoryBrowser


OWB Client User SchemaTarget

schemas

Code Generator


Repository ownerschema

Design Center



Generatedcode

OWB Run-Time Components (continued)Control Center ManagerThis component provides the user interface for centrally managing all aspects of deployment and execution. You can select objects for deployment, determine how you want those objects to be deployed, or let Warehouse Builder determine the best choice for deployment and then execute the deployed objects. You can manage the life cycle of your system with Control Center Manager’s update capabilities.Control Center ServiceControl Center Service enables deployment of OWB mappings and processes to databases and the execution of these mappings and processes. Control Center Service is like an “execution agent,” outside of the database, that can execute and monitor things that cannot be run directly in the database, such as PL*SQL scripts, SQL*Loader, and shell scripts.Target SchemasThe target schema contains deployed objects (for tables, dimensions, cubes, mappings, and so on). It contains synonyms of the repository owner’s run-time objects, enabling auditing. The target schema is granted access to the repository packages needed to log audit messages during execution. Multiple target schemas can be related to a repository.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Loose Coupling of Metadatawith Physical Implementations

One logical model,multiple run times

DevelopmentPhysical

implementation

Configuration 1: Its Control Center points to the Development run-time location.

ProductionPhysical

implementation

MigrationNew software

release

Configuration 2: Its Control Center points to the Production run-time location.

Configuration 3: Its Control Center points to the Migration run-time location.

Loose Coupling of Metadata with Physical ImplementationsIn OWB, logical design and physical implementation are “loosely coupled.” This loose coupling enables a single logical design to drive multiple physical implementations, without the need to change your logical design. One Logical Metadata Model for Multiple Run TimesDefine the metadata model once. Define a named configuration (holding physical information for objects) for each of your run times. Associate each configuration’s Control Center with a target run-time location. In a multideployment scenario, you can change location details (local or remote), without the need to change the design. You need not remember physical connection details of the target environment each time you deploy the objects to the target schema. The connection details are stored in the location definition. Also, the control center that you use determines where you deploy the objects.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Multiple Named Configurations: Preview

PhysicalconfigurationDevelopment

- No logging- Nonparallel- Tablespace DEV_DATA- Table EMP Location <abc>

- No logging- Parallel- Tablespace PROD_DATA- Table EMP Location <abc>

Logicaldesign

• Named configurations for multiple deployments• No need to write scripts to change tablespace

names, and so on(Multiple named

configurations and locations covered

in the Part 2 course)

PhysicalconfigurationProduction

Multiple Named Configurations: Preview Named configurations enable easier management of multiple deployments.

• Each named configuration can specify physical object properties to match the environment (for example, tablespace for a table and audit level for a mapping).

• A default configuration is automatically created and associated with a default Control Center (created for you in this course).

One object can have multiple physical configurations. For example, you can configure all objects for your development environment to deploy into the DEV_DATA tablespace. For the production environment, define the tablespace name to be PROD_DATA. The logical definition of the object does not change.Configurations Scoped Per User, Per ProjectActive configuration: The configuration that you are currently using and deploying to. A configuration indicates which Control Center it is using, and consequently which location. The active configuration is set per user, per project.Default configuration: The default configuration for a project. This is the configuration any newly created object will inherit.Note: Multiple named configurations and multiple locations are covered in detail in the Oracle Warehouse Builder 10g: Implementation Part 2 course.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




OWB Mapping

• ETL involves the movement andtransformation of data from yoursources to your targets.

• Use OWB mappings to specify which source data objects provide data to which target data objects.

• Mapping definitions reside in target modules.

Relational or flat file module

Table

Staging areamodule

ColumnColumn

Table

Warehouse ordata mart module

ColumnColumn

Map Map

OWB MappingA mapping graphically describes a series of operations that together extract data from sources, transform that data as necessary, and load the data into target tables.Mapping StepsThe general steps for creating OWB mappings are as follows:

• Create or select an existing source module.• Create objects or import them into the source module.• Create or select an existing warehouse module.• Create or select existing warehouse objects.• Map source objects to warehouse objects.• Generate code from the mapping.• Deploy the code to the database.• Execute the mapping to perform ETL.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Executing a Mapping at a Target Location

DesignRepository

DesignCenterDesign

CenterDesignCenter

After connecting to a Design Repository, Design Center users can launch Control Center Manager, using a configuration thatpoints to a ControlCenter on a remoterun-time machine.

ControlCtr. Mgr. Control

Ctr. Mgr.

ControlCtr. Mgr.

Configuration 1

RuntimeRepositoryholdingrun-time &deploymetadata

Data to be loaded

Configuration 2

Configurationpoints to a remoteControl Center.

Control Center

Ctrl. Ctr. Svce.

SQLLDR

Active

Executing a Mapping at a Target LocationThis diagram represents a simple default setup:

• Design Repository and Control Center on the same host machine, accessed by multiple users

• Run-time system in another databaseIn this example, three people run the OWB Design Center on their computers, connecting to the same Design Repository. When connected to the Design Repository, they can launch the Control Center Manager, using a configuration associated with a Control Center Service, which physically runs on a remote run-time machine (location).Note: Configurations are scoped per project, per user. In this simple example, all three Design Center users use the same configuration. They can each have their own configurations pointing to different control centers that, in turn, point to different target run-time locations.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Classroom Stand-alone Configuration

A single database hostseverything locally:

• OWB Design Center • Design repository• Repository owner, users• Control Center• Source data• Warehouse target

You

Classroom Stand-alone ConfigurationIn contrast to any likely production system, the classroom configuration provides an entire self-contained OWB system on each student’s computer.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Independent Versus Dependent Marts

Independent Dependent

Data marts

Data marts

Ware-house

Sources Sources

Independent Versus Dependent MartsIndependent Data MartsIndependent data marts are supplied directly from source systems. There are several issues with independent data marts:

• Can you guarantee consistency of the data between the marts? • Can you guarantee that the rules that are applied to the data entering the mart are the

same? • Can you take related data from any of these marts and make sensible comparisons?

Careful and consistent methods are needed to ensure that the answer to all these questions is “yes.” Independent marts also have benefits, being easier and less complex to build.Dependent Data MartsDependent data marts rely on the enterprisewide warehouse for their data, which may be more challenging and time-consuming to build, but provide the following benefits:

• The consistency of data in any data mart is guaranteed.• Database management is easier because rules for backup, recovery, and archiving apply

to all marts.• Detailed data can be stored in the enterprise warehouse, and data marts can share the

enterprise information, enabling them to be smaller and more manageable.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Independent Data Mart

Sales or marketingdata mart

Operationalsystems

External data

Flat files

Independent Data MartIndependent data marts are stand-alone systems that are not based on existing data warehouses. They extract data directly from operational or external sources of data. Independent data marts have the following characteristics:

• The sources are operational systems and external sources.• The ETL process is difficult. Because independent data marts extract data from unclean

or inconsistent data sources, efforts are directed toward error processing and integration of data.

• The data mart is built to satisfy analytical needs. The creation of independent data marts is often driven by the need for a quick solution to analysis demands.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Dependent Data Mart

Data warehouse

Marketing

Sales

Finance

Data mart

Marketing

Sales

Finance

HumanResources

Operationalsystems

External data

Flat files

Dependent Data MartDependent data marts have the following characteristics:

• The source is the warehouse. Dependent data marts rely on the data warehouse for content.

• The ETL process is simpler because the source is simpler in structure. Dependent data marts extract data from a central data warehouse that has already been created. The dependent data mart would simply require data to be moved from one database to another if the data warehouse were a structurally sound star schema. However, there is typically a need to do dimensional work and perform aggregation.

• The data mart is part of the enterprise plan. Dependent data marts are usually built to achieve improved performance and availability, better control, and lower telecommunication costs resulting from local access to data that is relevant to a specific department.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Purpose of a Staging Area

Extract

Operational

External

Flat files

Server logfiles

E

Transform/Load

TLStaging areas

Transformations

Enterprise model

(atomic data)

Publish Subscribe

Portal

Access layers

Metadata repository

Dependentdata marts

RDBMS

B2C

B2B

TL

Purpose of a Staging AreaYou may optionally use one or more staging areas in your warehousing environment. A staging area provides a common platform to address:

• Different topologies:- Operational systems- Networks- Protocols

• Multiple sources:- Different load windows- Minimal impact on source systems- A common or tunable engine for data movement and transformation

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Data Staging Area

The data staging area:• Is the construction site for the warehouse• Is required by many implementations• Can be composed of operational data stores

(ODS), flat files, or relational server tables• Is frequently configured as multitier staging

Extract

Transform

Load(Transport)

Operationalsystems

Data staging area Warehouse

Data Staging AreaRalph Kimball, who is an authority in data warehousing, calls the data staging area the construction site for the warehouse. This is where much of the data transformation and cleansing takes place.A staging area is a typical requirement of warehouse implementations. It can be an operational data store environment, a set of flat files, a series of tables in a relational database server, or proprietary data structures that are used by data staging tools. Staging tables are not mandatory with Oracle Warehouse Builder.You can employ multitier staging that reconciles data before and after the transformation process, and before data is loaded into the warehouse. As many as three tiers are possible from the operational server to the staging area and then to the warehouse server.Note: Some ETL tools stage data internally and do not require a separate staging area.In this course, you use staging tables.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Warehouse envt.

Warehouse environmentOper. envt.

Remote Staging Model

Warehouse

The data staging area within the warehouse environment:

Extract,Transform,

LoadTransform

Load

The data staging area in its own environment, avoiding negative impact on the warehouse environment:

Operationalsystem

Data staging area

Staging envt.Oper. envt.

WarehouseExtract,

Transform,Load

Transform

Load

Operationalsystem

Data stagingarea

Transform

Remote Staging ModelYou can choose to extract data from the operational environment and transport it to the warehouse environment for transformation processing. You can optionally execute some transformation processing during the extraction and transportation from the operational environment to the warehouse environment. You can then execute the bulk of transformation processing in the warehouse environment’s staging area.Choosing a ModelThe model that you choose depends on operational and warehouse requirements, system availability, connectivity bandwidth, gateway access, and the volume of data to be moved or transformed.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




On-Site Staging Model

The data staging area within the operational environment, possibly impacting the operational system:

Operational environment Warehouse environment

Extract

Transform

Load

WarehouseOperational

systemData staging area

On-Site Staging ModelAlternatively, you can choose to perform the cleansing, transformation, and summarization processes locally in the operational environment and then extract data to the staging area. This model conflicts with the day-to-day working of the operational system. If chosen, this model’s process should be executed when the operational system is idle or less used. This model is not recommended.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




B2C

B2B

TL

Purpose of an Enterprise Model

Extract

Operational

External

Flat files

E

Transform/Load

TL

Staging areas

Transformations

Publish SubscribePortal

Access layers

Metadata repository

Dependent data martsFederated data warehouse

RDBMS

Enterprise model

(atomic data)Server logfiles

Purpose of an Enterprise ModelAn alternative approach to independent data marts is the employment of an enterprise model that supplies data to dependent data marts. An enterprise model serves to establish:

• Semantic resolution among multiple source systems• Granularity of data• Strategies for:

- Keys: Natural and surrogate, as defined by:- Surrogate (Synthetic/Warehouse) key (that is, a generated key)- Production (Natural) key (that is, a source key)- Smart (Production/Natural) key (that is, a key with meaning)

- Versioning: History, row-level lineage- Updating (slowly changing dimensions)

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Course: Predefined and New ObjectsFlat file source module: FILE_SOURCE

GEOGRAPHY.TXT

DB module: HR

Target module: STAGING_AREA

Target user:STAGING_USER

External table:GEOG_EXT

Staging table:LOAD_STG_GEOG

Target module: SALES_WH

Target user: SALES_WH

* Create the CHANNELS dimension by using a wizard.* Create the PRODUCTS dimension by using an editor.* Create the TIMES dimension by using the Time Wizard.CUSTOMERS and PROMOTIONS dimensions are predefined.

* Create the SALES cube by using a wizard.* Design the ETL mapping to load the PRODUCTS dimension.

(The other dimension-loading mappings are predefined.)* Design the mapping to load the SALES cube.

Sales

Customers Channels

Promotions

Times

Products

DB source module: XSALES

Channels, Promotions,Products, Addresses,Categories, Cities,Countries, Customers,Regions, Promo-subcategories, Promo-categories, Orders,Order_items

Tables from the HR schema

Mappings

= Items with the check mark are predefined.

Mapping

Course: Predefined and New ObjectsThe diagram in the slide shows the objects that you define during the course, as well as the predefined objects in the CLASS_PROJECT project that are created for you when you import the mdl file.Flat File Source for External Table That Populates Staging TableYou define a FILE_SOURCE module that points to a flat file. You define a STAGING_AREA target module. You define an external table referencing the flat file, and define a mapping that populates a staging table from the external table.Note: The staging table is not used further in this course.Database Source Module Populates Dimensions and CubeA predefined XSALES source module points to an XSALES schema whose tables serve as the sources for mappings that populate your dimensions and a cube.Database Module for Data Profiling LessonsYou define an HR module pointing to the HR schema to practice data profiling.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




OMB*Plus tcl Scripting Within Design Client

You can run OMB*Plus within the Design Center client, or in a stand-alone command-line mode.

You can run OMB*Plus tcl scripts to perform any function available in the Design Center graphical interface. (For example, create, modify, delete, import, or examine your OWB metadata.)

OMB*Plus tcl ScriptingOMB*Plus provides another layer of access to the functionality provided in Warehouse Builder. Using OMB*Plus and the scripting language documented in the Warehouse Builder Scripting Reference Guide, you can access all the functions available from the Design Center graphical interface.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Launching OMB*Plusfrom the Command Line

Note: The OMB*Plus session running within the Design Center shares the login credentials with the Design Center; you cannot log in (OMBCONNECT) or disconnect in that OMB*Plus session.

Launching OMB*Plus from the Command LineYou run the scripts using the OMB*Plus scripting tool that is accessible from the Warehouse Builder program folder. Another method for importing metadata definitions into Warehouse Builder is to import an mdl file that has been exported from another Warehouse Builder project.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Summary

In this lesson, you should have learned how to:• Describe various design time and run-time

configurations• Describe the Warehouse Builder repository

architecture, users, and owners• Explain the benefits of warehouse staging areas• Describe the course data sources and targets• Import metadata by using tcl scripts

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 2-1:Importing Metadata

This practice covers the following topics:• Logging in as the repository owner (rep_owner)• Using the Metadata Import utility to import the mdl

file that creates the partially predefined CLASS_PROJECT

• Examining the partially predefined metadata in CLASS_PROJECT

Practice 2-1: Importing MetadataIn this practice, you log in to the Design Center as rep_owner, open the OMB*Plus panel, and run tcl scripts to create the partially predefined CLASS_PROJECT used in this course’s remaining lessons.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y



Defining Source Metadata

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Objectives

After completing this lesson, you should be able to do the following:• Define and create source modules• Specify source data from flat files• Specify source data from relational database

tables• Import source object metadata into the source

modules

ObjectivesThis lesson introduces the first task in building an Oracle Warehouse Builder (also called as OWB or Warehouse Builder) data warehouse: defining data sources. You learn how to use OWB wizards to create source modules and import metadata into them.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Course Progress Report

1. Define the source metadata.

2. Ensure data quality usingdata profiling.

3. Define staging area metadata.

4. Derive data rules and run correction mappings.

5. Define a relational dimensional model.

6. Create a process flow.

7. Deploy the mappings.

8. Execute or run the mappings.

9. View the data.

Course Progress Report1. Define the source metadata: Create the source module and import the metadata. In the

case of flat files, importing involves sampling of the flat file.2. Ensure data quality using data profiling: You profile the source metadata that you

defined in step 1. You analyze the results of data profiling in tabular or graphical format. 3. Define the staging area metadata: Create a staging module, create staging tables, use the

metadata to define the mappings, and deploy and execute the mappings. 4. Derive data rules and run correction mappings: In a real-life scenario, step 4

immediately follows step 2. In this course, step 3 is inserted to introduce you to OWB mappings, which are used in step 4.

5. Define a relational dimensional model: You define the dimensions and cube used for this course. You also define the mappings to load the dimension and cube.

6. Create a process flow: Process flows interrelate mappings and activities external to Warehouse Builder.

7. Deploy the mappings: Deploying a mapping includes generating the PL/SQL, SQL*Loader, or ABAP (Advanced Business Application Programming) script, if necessary.

8. Execute or run the mappings: Starting a mapping involves generating a script and deploying it.

9. View the data: View the data by using the Data Viewer.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Metadata to Data

1. Chart the metadata of the object.

2. Import the metadata. (This gives you only the data definition.)

3. Use the metadata to define the mapping.

4. Deploy and execute the mapping to load the data.

Metadata to Data1. Chart the metadata of the object: A Warehouse Builder project is the largest storage

object within the Warehouse Builder design repository. In this course, you have a predefined project called CLASS_PROJECT. You begin designing and modeling your system by defining modules. In Warehouse Builder, you create source modules to store definitions from different source systems. You can create source modules for Oracle databases, non-Oracle databases, flat files, and SAP applications.

2. Import the metadata (data definitions): You import definitions from different data sources. You import these definitions into the source modules. These definitions are stored within projects in the Warehouse Builder repository.

3. Use the metadata to define the mapping: Create the data movement and transformation logic, also known as extract, transform, and load (ETL) logic. You can use the following components to define and organize data movement and transformation in Warehouse Builder:

- Transformations- Mappings- Process flows

4. Deploy and execute the mappings to load the data: You deploy the design to the target environment and then execute mappings and process flows that load the data.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Source Module

• A module is a logical grouping of related objects under a single, referential heading.

• Source modules hold metadata describing source systems from which you extract data.

Source ModuleA part of designing your warehouse by using Oracle Warehouse Builder includes defining the source modules and objects that are used to provide information and data to your finished data warehouse. In Warehouse Builder, you create source modules to store definitions from different source systems. You can create source modules for:

• Oracle databases• Non-Oracle databases (such as Sybase, Informix, and ODBC [Open Database

Connectivity])• Flat files (comma-delimited, fixed-length, and multirecord flat files)• Applications (such as SAP and Oracle E-Business Suite)

To populate the source module with source schema information, you import source metadata. None of the activities that create or import metadata move any data. Data is moved when you perform ETL, and not when you capture metadata.Note: Importing metadata from a database outside of the database that is used to store the OWB repository (either Oracle or non-Oracle) requires a database link to bring in metadata about existing source objects.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Lesson Data Sources

Flat file source

FILE_SOURCE

GEOGRAPHY.txt (delimited)

Relational source

Employees

Departments

HR

Lesson Data SourcesDefining SourcesIn this lesson, you focus on defining the structure of the source objects.Defining the structure of the source objects for this course involves the following activities:

• Defining and creating a source module (FILE_SOURCE) for flat files- Specifying source data from flat file (GEOGRAPHY.txt)

• Defining and creating a source module for relational database sources (HR)- Specifying source schema (HR)

• Importing source object metadata into the source modules O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Creating a Flat File Source Module

Creating a Flat File Source ModuleModules are storage objects within projects using which you can logically group source and target object definitions. You create flat file modules to store definitions of flat files you import.To create a flat file source module, perform the following steps:

1. In the Design Center, in the Project Explorer panel, expand CLASS_PROJECT.2. Right-click the Files node, and select New. The Create Module Wizard is launched.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Using the Create Module Wizard

Using the Create Module WizardAs with other Oracle Warehouse Builder wizards, the first page of the wizard previews the steps for creating a new module.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Module Wizard: Nameand Description

Create Module Wizard: Name and DescriptionOn the wizard’s Name and Description page, provide the following information about the source module:

• Name: Assign a unique name to the module.• Description: Enter an optional description for your module.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Module Wizard: Connection Information

Create Module Wizard: Connection InformationOn the wizard’s Connection Information page, you can create a new location for the flat file or choose from a list of previously specified locations.Existing LocationTo use an existing location, from the Location drop-down list, select a location. Then, you see the fields populated with the connection information. New LocationTo create a new location, click Edit.Note: If you have more than one flat file, you can place each file in its own separate module. However, these separate modules would not produce a performance gain in the generated code. Also, a module can have only one physical path to import metadata per import. Therefore, if you have two or more flat files that must reside in different paths, then you need multiple modules (one for each path) or change the path.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Editing File System Location

Editing File System LocationLocations are specific to a type of module, such as the Oracle database, SAP application, or flat file. In a flat file source module, location is the path or the drive and directory in the file system where the flat files reside. Use this page to specify a location for the flat file source module. Perform the following steps:

1. For this course, rename the location from FILE_SOURCE_LOCATION1 to FILE_SOURCE_LOCATION.

2. Click Browse, and select the drive and the directory that contains the flat file. Click OK.Note: In the Path field, provide only the drive and the directory where the flat file resides; the name of the flat file is not visible here.

3. After you have performed the steps using the Create Module Wizard, on the Connection Information page, select the “Import after finish” check box to automatically launch the Import Metadata Wizard.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Module Wizard: Summary

Create Module Wizard: SummaryThe Summary page summarizes the information you provided on each of the wizard pages. The wizard creates the flat file module and inserts the module name in the Project Explorer under the Files node and proceeds to importing the metadata by using the Import Metadata Wizard.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Metadata to Data





Metadata to DataAfter completing step 1 of charting the metadata, you are now ready to import the metadata.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Import Metadata Wizard: Welcome

Import Metadata Wizard: WelcomeUsing the Create Module Wizard, you created a flat file source module (FILE_SOURCE). Choosing “Import after finish” launches the Import Metadata Wizard.The wizard’s Welcome page lists the steps through which the wizard guides you.Note: If you do not select the “Import after finish” check box on the Connection Information page of the Create Module Wizard, then you can explicitly invoke the Import Metadata Wizard. To do this, in the Design Center, expand CLASS_PROJECT > Files. Right-click FILE_SOURCE, and select Import. The Import Metadata Wizard is launched.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Importing from Flat Files

Importing from Flat FilesUse the Filter Information page to indicate the file type to be selected on the next page of the Import Metadata Wizard:

• All data files• Data files matching this pattern

You can optionally specify pattern-matching filtering information.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Selecting the Flat Files

Selecting the Flat FilesUse the arrow buttons to move objects from the Available list to the Selected list.Note: Because these are nonrelational flat files, the option for importing secondary tables is unavailable.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Collecting Geography Metadata Information

Collecting Geography Metadata InformationResponding to a Red Cross IndicatorA red cross indicates that there is no metadata associated yet with the file. You can respond to the red cross in either of the following ways:

• Use the Sample button to invoke the Flat File Sample Wizard to define the format of the import file.

• Apply an existing file structure by using the Same As field indicating that Warehouse Builder can use previously captured metadata to describe this file.

You sample the GEOGRAPHY.txt file by invoking the Flat File Sample Wizard.Responding to a Green Check Mark IndicatorA green check mark indicates that OWB knows how to read the file.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Flat File Sample Wizard: Welcome

Flat File Sample Wizard: WelcomeAfter creating the flat file module, you import flat file definitions into Warehouse Builder. The Import Metadata Wizard guides you through the process of importing metadata objects. Each time you use the Import Metadata Wizard to import metadata from existing flat files, the Import Metadata Wizard launches the Flat File Sample Wizard. When the data source is a flat file, the user assists in the process of creating the metadata. This process is called sampling. Use the Flat File Sample Wizard to inspect and document metadata for flat files.The wizard’s Welcome page lists the steps through which the wizard guides you.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Describing the File

Describing the FileUse the Flat File Sample Wizard’s Name page to specify the file’s name and the number of rows to sample.NameThe name defaults to the sampled file’s name.DescriptionYou can optionally describe the file that is being sampled.Number of Characters to SampleYou can limit the number of sampled rows. The number of rows to sample defaults to 10,000.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Record Organization

Record OrganizationUse the Flat File Sample Wizard’s Record Organization page to indicate how records are to be organized in the file that you are sampling. Select one of the following two options to indicate how the length of each record is determined:Records delimited by: Select this option if the end of each record is designated by a delimiter. Then specify that record delimiter. Accept the default record delimiter, that is, carriage return (<CR>), or enter a new value.Record length (in characters): Select this option if each record in the file is of the same length. Then specify the number of characters in each record. For files with multibyte characters, count a multibyte character as one character.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Record Organization

Record Organization (continued)Specifying Logical RecordsA logical record is a structure for grouping one or more physical records that behave as a single record. You can use the Flat File Sample Wizard to sample files that are composed of logical records that correspond to multiple physical records. If the file contains logical records, then select “File contains logical records.” Then select one of the following options to describe the file:

• Number of Physical Records per Logical Record• End Character of the Current Physical Record• Start Character of the Next Physical Record

The default selection is one physical record per logical record.O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Selecting the File Format

Selecting the File FormatUsing the Flat File Sample Wizard’s File Format page, you can specify the file format to be Delimited or Fixed Length. You can also specify the delimiter type and enclosure type. In the example in the slide, it is appropriate to accept the default values of delimited file format, comma-field delimiter, and double quotation marks (“ ”) enclosures.The lower portion of the page shows a sampling of data from the flat file.DelimitedField delimiters designate where one field ends and another begins. The fields are separated by delimiters, such as commas (comma-separated values [CSV]), white space (any number of tabs or spaces), colons, tabs, or space. You can enter a field delimiter or select one from the drop-down list. The drop-down list displays common field delimiters. Fixed LengthData is aligned into fields of specified width.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




File Layout

File LayoutOn the File Layout page of the Flat File Sample Wizard, define the input file’s layout.Rows to SkipYou can specify the number of rows to skip.Record Types

• Single record type files• Multiple record type files O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Modifying Field Information

Modifying Field InformationThe Field Properties page shows detailed SQL*Loader and SQL properties about each field, such as field name, field type, and length.Using the First Record’s Values as Field NamesYou can choose to use the first record’s values as the field names if the flat file’s first record is a header. This is true of the GEOGRAPHY.txt file.Note: The Length field is blank and the generated SQL*Loader code takes the default maximum length for the given data type. For example, the maximum length for CHAR is 255 by default. If the sampler detects a sampled row that has, for example, a length of 256, then 256 will be filled in.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Summary for Geography Metadata Sampling

Summary for Geography Metadata SamplingThis window summarizes your specifications for the sampling of the GEOGRAPHY.txt file.You can expand the File, Record Organization, and Record items to review the parameters that you have chosen for the file. Click Finish.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 3-1: Create a Flat FileSource Module

This practice covers the following topics:• Creating a flat file source module• Importing the GEOGRAPHY.txt metadata from a

flat file

Practice 3-1: Create a Flat File Source ModuleIn this practice, you create a flat file source module. The flat file module stores definitions of the flat files. To create a flat file module, you use the Create Module Wizard. After you create the flat file module, you import the GEOGRAPHY.txt metadata from a flat file by using the Import Metadata Wizard.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Lesson Data Sources

Flat file sources

FILE_SOURCE

GEOGRAPHY.txt (delimited)

Relational source

Employees

Departments

HR

Lesson Data SourcesSo far you have examined how to use the OWB Create Module Wizard to create a source module for flat files. You also learned how to use the OWB Import Metadata Wizard to import source metadata from flat files. The Import Metadata Wizard launches the Flat File Sample Wizard. You use the Flat File Sample Wizard as an aid in defining metadata from flat files. The Flat File Sample Wizard stores the metadata you define in the Warehouse Builder repository.Further in this lesson, you learn the following:

• Defining and creating an Oracle data source module (HR)• Using the Import Metadata Wizard to import metadata from a database into the Oracle

database–based source moduleO

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Creating an Oracle Source Module

Creating an Oracle Source ModuleYou have created a source module for defining flat file sources. Now you define and create a source module for relational database sources.To create the HR database source module, perform the following steps:

1. In the Project Explorer, expand CLASS_PROJECT > Databases.2. Right-click Oracle, and select New. The Create Module Wizard is launched.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y





Create Module Wizard: Name and DescriptionOn the Name and Description page, provide the following information:

• The module name• The module status (Development, Quality Assurance, or Production). The module status is

only a comment field that does not affect code generation.• The module type. You can select one of the two options: Data Source or Warehouse

Target. There are no differences; this is for documentation, so that it is simpler to see which one is used as a source. In this lesson, you create an Oracle source module. To create a source module, select Data Source. In the lesson titled “Defining Staging Metadata and Mapping Tables,” you select the Warehouse Target option to create a target module.

• An optional descriptionO

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly





Create Module Wizard: Connection InformationUse this page to specify an existing location or define a new one for the module by clicking Edit.Purpose of LocationThe database location establishes a connection to the database from which the metadata is to be extracted. VersionSelect the database version 8.1, 9.0, 9.2, 10.1, or 10.2. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Editing the Oracle Database Location

Editing the Oracle Database LocationOn the Edit Oracle Database Location page, provide the connection information (username, password, host, port, and service name) that specifies the source of the metadata. Name: Enter a unique name.Description: A description is optional.Type: There are three connection types:

• Host:Port:Service Name - User Name: <Username with access to the source database>- Password: <Password that corresponds to the username for the source database>- Host: <localhost or machine name>- Port: 1521- Service: <orcl Oracle Service Name (SID)>

• Database Link: This hides the connection details from the user. Use a predefined database link to allow database administrator (DBA) control over what schema to access.

• SQL*NET Connection: This enables you to use the logical name of a server rather than of the physical node. It also enables you to refer to Real Application Clusters (RAC) where you use TNS Names entries and do not refer to a direct single node.

Test the connection: Click Test Connection to test the connection.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Finishing Module Creation and Proceeding to Import

Finishing Module Creation and Proceeding to ImportStarting the Import Metadata WizardThe “Import after finish” check box is selected by default. Click Finish to create the source module and proceed directly to the Import Metadata Wizard.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Import Metadata Wizard: Filter Information

Import Metadata Wizard: Filter InformationUse the Filter Information page to limit your database query to retrieve only those source objects that you want to consider for importing into your Oracle Warehouse Builder source design.

• Object type: Select from the options (Table, Dimension, ExternalTable, View, Use a synonym to look up objects, Sequence, and so on) in this box to retrieve a list of only those database objects that you want to import. For example, select Table if you want to import only the table that holds employee information. Select the “Use a synonym to look up objects” check box to import objects by synonym.

• Use the name field to make wildcard selections: Use this option to filter the list of database objects by the character string that you specify.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Selecting the Tables for Import

Selecting the Tables for ImportIn the Available list, you see a list of objects depending on what you selected on the wizard’s Filter Information page. Use the arrow buttons to move available objects to the Selected list.Related Tables Also SelectedAny tables with foreign key relations to your selection are also selected, depending on the chosen foreign key level. This selects both the parent and child tables.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Completing the Metadata Import

Completing the Metadata ImportWhen the metadata import process starts, an Importing Progress dialog box appears. On completion, an Import Results dialog box appears.Click OK to accept the import results. Click Undo to abandon any imports.Note: The Import Results dialog box in this slide reports that the creation of all objects is successful.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Examining the Imported Metadata

Examining the Imported MetadataWhen the metadata import is completed for your new source module, you can expand the HR module and examine the metadata that is imported.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Viewing Data Using the Data Viewer

Viewing Data Using the Data ViewerWith the Data Viewer, you can see the data that is stored in the data object. To view the table data in the HR schema, in the Project Explorer, right-click the data object and select Data. The Data Viewer pops up with the data displayed in tabular format.Note: You can see data in the data viewer because the HR source schema is populated with data.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Difference Between Obtaining Relational and Flat File Source Metadata

Flat filesource module:FILE_SOURCE

Staging area

The flat file integrator samplesfile data.

The database link extracts relational

table metadata.

Employees

Difference Between Obtaining Relational and Flat File Source MetadataYou create two modules for representing this case-study source data because Warehouse Builder uses different methods for obtaining metadata from relational tables and flat files.Relational Tables as SourceWhen the data source is a table, the owning database stores extensive information about the table, such as the table name and column names. Warehouse Builder simply reads this catalog information and stores it.Flat Files as SourceIn contrast, when the data source is a file, the user assists in the process of creating the metadata. This process is called sampling. The flat file integrator is a component of Warehouse Builder that is dedicated to extracting data from flat files. The flat file integrator generates a SQL*Loader control script to read data from a flat file and write it to the database. Alternatively, you can use external tables for a better parallel load process.Warehouse Builder supports the sampling of three kinds of flat files:

• Character-delimited files• Fixed-length files• Multirecord files

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Summary

In this lesson, you should have learned how to:• Create a flat file source module • Create an Oracle database module• Import the metadata by using the Import Metadata

Wizard

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 3-2: Create a Relational Database Source Module

This practice covers the following topics:• Creating an Oracle database module • Importing data from an Oracle source

Practice 3-2: Create a Relational Database Source ModuleIn this practice, you create an Oracle database module. Using the Import Metadata Wizard, you import data from the database schema. This practice uses the HR schema.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y



Ensuring Data Quality Using Data Profiling

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Objectives

After completing this lesson, you should be able to do the following:• Create a data profile• Profile the data• View profile results• Analyze profile results

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y






2. Ensure data quality using data profiling.






8. Execute or run the mappings.9. View the data.

Course Progress ReportExamine Oracle Warehouse Builder data profiling features that help maintain the quality of both your data and metadata.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




What Is Data Profiling?

• Data profiling is a data analysis tool.• It provides data cleansing and schema correction

methods.• Using data profiling, you can:

– Profile data from any source that Warehouse Builder can access

– Explore data profiling results in tabular or graphical format

– Drill down to the actual data related to any profiling result

– Derive data rules– Use a data rule to create data correction

What Is Data Profiling?Data profiling is a data analysis method available in Oracle Warehouse Builder (also called as Warehouse Builder or OWB) that can be used to discover and measure anomalies in data before you perform extract, transform, and load (ETL). In OWB, you can profile any set of tables and review the profiling results in the interactive or reporting environment.In this lesson, you profile a data source and analyze the results of data profiling in tabular or graphical format. Using data profiling, you can drill down to the actual data related to profiling results. For more information about deriving data rules and correction, see the lesson titled “Deriving Data Rules and Running Correction Mappings.”

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Steps in Data Profiling

1. Create a data profile.2. Profile the data.3. View and analyze the profile results.

Steps in Data ProfilingBefore beginning data profiling, you must first identify the data objects that you want to target. Select areas of your data where quality is most essential.After you have chosen the objects that you want to profile, perform the following steps to guide you through the profiling process:

1. Create the data profile. 2. Profile the data.3. Explore the data profiling results in tabular or graphical format. Drill down to the actual

data related to any profiling result.O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Creating a Data Profile

• A data profile is an object that you create in the navigation tree in the Design Center.

• This data profile contains the definitions and settings necessary for profiling.

Creating a Data ProfileA data profile is a user-configurable entity that contains the set of metadata objects to be profiled and a reference to the data to be profiled, the settings controlling the data profiling operation, the results returned after you profile the data, and the correction information. In this course, you create the HR_DP data profile. To create a data profile, perform the following steps:

1. In the Design Center, in the Project Explorer panel, expand CLASS_PROJECT.2. Right-click the Data Profiles node. Select New. The Create Data Profile Wizard is

launched.O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Create Data Profile Wizard:Name and Description

Create Data Profile Wizard: Name and DescriptionOn the Name and Description page, you provide the following information about the data profile:

• Name: Assign a unique name to the data profile.• Description: Enter an optional description for the data profile.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Data Profile Wizard: Select Objects

Identify and select the objects where data quality is most essential.

Create Data Profile Wizard: Select ObjectsIdentify and select the objects where data quality is most essential. Select areas of your data where you think quality is most essential. For example, in the HR data source, you decide that the Employees table is the most important among other tables with respect to data quality. The table may contain data about employees in an incorrect format.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Data Profile Wizard: Summary

Create Data Profile Wizard: SummaryThe summary page displays the objects that you have selected to profile. Review the summary page. Click Finish to create the data profile. The data profile is now created and added to the navigation tree. The Data Profile Editor is launched. Now you actually begin profiling your data.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y






Steps in Data ProfilingNo profiling has been performed yet. Creating a data profile is just the creation of a named data profile object in the navigation tree to store the results of a profiling job. You have until now created a data profile by using the Create Data Profile Wizard.Now you profile the data and learn how to use the Data Profile Editor.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Profiling the Data Usingthe Data Profile Editor

Profiling the Data Using the Data Profile EditorYou use the Data Profile Editor to profile the data. The Data Profile Editor provides a single access point for managing and viewing data profile information as well as correcting metadata and data. Clicking Finish on the Create Data Profile Wizard: Summary page launches the Data Profile Editor, with the Warehouse Builder Note dialog box, which guides you to profile the data. To profile the data, from the Profile menu in the Data Profile Editor, select Profile. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Data Profile Setup

Data Profile SetupIf profiling is executed for the first time, the user is prompted for the SYS login information to create a profiling workspace. A location for the data profiling schema is created and registered automatically. This is a one-time operation; subsequent profiling uses this workspace unless it is reset manually to another workspace. Alternatively, the profiling workspace schema can be created manually. Complete the following details on the Data Profile Setup page:

• Provide the password for the SYS user or provide details about any other account having SYSDBA privileges. Click Show Details. The name that you see for the schema defaults to <repository owner’s schema name>_PRF, and the default password is the repository owner’s password.

• Provide the name and password of the profiling target schema that you want to create. In this course, you use PROFILEWORKSPACE as the data profiling schema. The profiling target schema acts as a workspace where profiling is done.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Preparing the Profile

Preparing the ProfileAfter the data profile setup process completes, the Preparing Profile progress window appears. The progress indicates the different metadata objects that Warehouse Builder is creating to profile the data. If you chose to copy the data, this would include the mappings and so on.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Profiling Initiated

Profiling InitiatedThe actual profiling operation is asynchronous, making it possible for you to close the Data Profile Editor and continue with your other work in OWB, or even close OWB Design Center altogether. This is indicated by the Profiling Initiated message.From this point onward, you can see the status of your profiling operation in the Monitor Panel. In the Monitor Panel, you can view details about the currently running profiling event as well as the earlier profiling events. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Retrieving Profile Results

Retrieving Profile ResultsWhen the profiling operation completes, the Retrieve Profile Results dialog box appears. Click Yes to retrieve the profile results. This option is useful if you have previously profiled your data in the same data profile because it gives you control of when the new profiling results become visible in the Data Profile Editor. Profiling is now complete. The Monitor Panel changes the status to reflect this. The profiling results contain a variety of analytical and statistical information about the data. You can immediately drill down into anomalies and view the data that caused them. You can then determine what data was stored correctly, and what data needs to be corrected.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 4-1: Profile the Data

This practice covers the following topics:• Creating a data profile• Profiling the data

Practice 4-1: Profile the DataIn this practice, you create a data profile and profile the data. If you are executing the profile for the first time, the Data Profile Setup dialog box is displayed.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y






Steps in Data ProfilingYou now view the profiled data and see the different types of analysis that data profiling offers.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Types of Profiling

Data profiling offers three main types of analysis.

Data profiling Custom profiling

Referential analysisFunctional dependencyAttribute analysis

General Data type Unique

Pattern Domain

Orphans Childless

Redundant attributesJoins

Types of ProfilingNow that profiling is complete, you are ready to review the results of your work and explore the power of the OWB data profiling feature. Data profiling offers three main types of analysis:

• Attribute analysis • Functional dependency analysis• Referential analysis

Each type of analysis is explained in this lesson. You use the Profile Results Canvas and the Data Drill Panel extensively to discover the structure and semantics of your source data.In the Profile Results Canvas, you can view the results of the profiling. In the Data Drill Panel, you can click an aggregated data item and view the data results.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Attribute Analysis

Attribute analysis seeks to discover both general and detailed information about the structure and content of the data stored within a given column.




Pattern Domain

Orphans Childless


Attribute AnalysisAttribute analysis is a type of data profiling that deals with the analysis of the structure and content of the data for each data attribute. You can determine general statistics such as minimum, maximum, average of values; count of nulls; and distinct count. You can also discover patterns, analyze data types, perform domain analysis, and perform unique key analysis. Now you see examples of some of these.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Attribute Analysis: Glimpseof the Table DataNo profiling magic yet!

1

23

Attribute Analysis: Glimpse of the Table DataTo get the first glimpse of the data in the EMPLOYEES table and the structure of the table (number of columns, rows, and so on), perform the following steps:

1. In the Data Profile Editor, in the navigation tree on the left, ensure that the Profile Objects tab is selected.

2. Expand HR, and select EMPLOYEES.3. In the Profile Results Canvas, click the Profile Object tab. This tabbed page lists the

original data records in the EMPLOYEES table. Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Attribute Aggregation Analysis

A type of attribute analysis that produces general statistics of attribute values, such as minimum, maximum, average of values; count of nulls; and distinct counts.

1

2 34

Attribute Aggregation AnalysisOn the Aggregation tabbed page, all the essential measures are listed for each column: minimum values, maximum values, number of distinct values, null values, and so on. Some measures are available only for specific data types such as Average, Median, and Standard Deviation. To know what the maximum salary is, perform the following steps:

1. In the Profile Results Canvas, click the Aggregation tab. 2. Scroll to the SALARY row and view the corresponding Maximum column value.3. The value is hyperlinked, indicating that you can click it and drill down into the data. Click

the value.4. On the lower portion of the page, the Data Drill Panel changes to show you all the distinct

values of this column on the left. On the right, in the Data Drill Panel, the record for the SALARY value that you selected is displayed. (In this example, it is the employee with the maximum salary of 24,000.)

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Aggregation Graphical Results

See the distribution of employees across distinct departments in a graphical representation.

1

2

Aggregation Graphical ResultsTo see the distribution of employees across distinct departments in a graphical representation, perform the following steps:

1. In the Profile Results Canvas, click the Graphical tab.2. From the Column drop-down list, select DEPARTMENT_NAME.

Note: You can drill down to see employees in a particular department by clicking the bar of that department for which you want to see the details. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Determining the Six-Sigma Score

Determining the Six-Sigma score helps you to identify, understand, and eliminate the defects in the business processes that source the data.

Determining the Six-Sigma ScoreTo determine the Six-Sigma score for a particular column, perform the following steps:

1. On the Aggregation tabbed page, scroll right to view the Six-Sigma column. 2. Examine the Six-Sigma score for all the columns of the EMPLOYEES table.

This helps you in identifying, understanding, and eliminating the defects in the business processes that source the data.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Attribute Data Type Analysis

Explore the data types, length, precision, and scale of each of the columns.

1

2

3

4

Attribute Data Type AnalysisOn the Data Type tabbed page, you can explore the data types, length, precision, and scale of each of the columns. For each column, the documented (type, length) data is compared with the dominant one that is found by data profiling, and the percentage of rows that comply with the dominant measure is listed.

1. In the Profile Results Canvas, click the Data Type tab.2. Select DEPARTMENT_NAME, and examine the value for “%Dominant Datatype.” It

shows 99.1%, which means that there are a few records whose values are not of the VARCHAR2 type. Click VARCHAR2.

3. In the Data Drill Panel, you see that there is a record with DEPARTMENT_NAME as null.4. On the right, you see details for the null record.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Attribute Domain Analysis

The Domain tab is used to display results about the possible set of values that exist in a certain attribute.

1

2What does one do

with this finding?

Attribute Domain AnalysisOn the Domain tabbed page, you discover the domain values for a column. To find the domain for the JOB_ID column, perform the following steps:

1. In the Profile Results Canvas, click the Domain tab.2. Scroll down to view the JOB_ID column, and examine the value in the % Complaint

column. It shows 89%.In the Data Drill Panel, observe that 89 percent (5 rows) of the records are compliant with the five domain values: SH_CLERK, IT_PROG, SA_REP, PU_CLERK, and ST_CLERK. Observe (in the Data Drill Panel) that there are twelve records that do not comply with these values.Note: What does one do with this finding? What is the practical value? You learn how to correct these noncompliant values in the lesson titled “Deriving Data Rules and Running Correction Mappings.”

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Attribute Unique Key Analysis

Click the Unique Key tab for information about the existing unique keys.

1

23

4

Attribute Unique Key AnalysisWith the Unique Key tab, you can analyze the existing unique keys that were documented in the data dictionary and also the possible unique keys or key combinations found by data profiling. The % Unique value is shown for each of the unique keys.

1. In the Profile Results Canvas, click the Unique Key tab.2. Scroll down to the PHONE_NUMBER attribute.

Observe that the column is only 98% unique. This PHONE_NUMBER column can be a candidate for a unique key.

3. Click the hyperlinked Yes in the “Discovered?” column. 4. In the Data Drill Panel, select Not Compliant from the Distinct values drop-down list to

find the noncomplying records.For each phone number noncompliant value, you find corresponding records on the right.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Referential Analysis

Click the Referential tab for information about foreign keys.




Pattern Domain

Orphans Childless


Referential AnalysisYou have just completed attribute analysis and seen that attribute analysis looks for information about domains, data types, and unique values. In referential analysis, you determine the relationship between attributes. You see the existing foreign keys that were documented in the data dictionary as well as relationships found by data profiling. For each relationship, you can:

• See the measures of compliance• Find out noncompliant records, such as orphans and childless records

You find two subtabs in referential profiling, which are not found in other types of profiling:• Joins• Redundant Columns

The Redundant Columns subtabbed page displays information about columns in the child table that are also contained in the primary table.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Property Inspector

Property InspectorThe Property Inspector enables you to define the configuration parameters for the data profiling operation. Many types of data profiling operations rely on the configuration parameters to set the limits and the assumptions of analysis.In this slide, the Use in Relationship Discovery parameter is set. Similarly, you can specify values for other properties in the Property Inspector.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Performing Referential Analysis

2

1

3

Performing Referential AnalysisTo see the existing foreign keys, perform the following steps:

1. Click the Referential tab.2. Scroll down to the JOB_ID attribute.

Observe that it is related to JOBS.JOB_ID and the % Compliant column shows 98%, which means that there are some records that did not comply with the foreign key relationship that you discovered. Note the relationship name for the JOB_ID foreign key relationship. In the screenshot, it is FK_6; but it may be different for your setup.

3. Click the hyperlinked Yes in the “Discovered?” column to drill down into the data.O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Referential Analysis: Noncompliant

1

2 3

Referential Analysis: NoncompliantTo view the noncompliant or orphan records in a graphical manner, perform the following steps:

1. Click the Graphical subtab on the Referential tabbed page. 2. Select FK_6 (the foreign key relationship you discovered in the previous slide) from the

Reference drop-down list.3. Select Non Compliant from the Property drop-down list.

In the graphical representation, you find that two records in the EMPLOYEES table are orphans because their JOB_ID values are not found in the related table, JOBS.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Joins Subtab on the Referential Page

Displays a join analysis of the reference selected from the Reference drop-down list

1

2

3

Joins Subtab on the Referential PageWhen you click the Referential tab, you see two additional subtabs, Joins and Redundant Columns, in the lower part of the Profile Results Canvas. These subtabs are not found when you select Functional Dependency, Profile Object, Aggregation, or any other tab.To display the joins analysis, perform the following steps:

1. Click the Joins subtab.2. Select FK_6 from the Reference drop-down list.

Notice that each outcome in the diagram can be clicked to drill down into the data.3. Click the Orphans hyperlink. The Data Drill Panel shows the two orphan records.

At a glance, you can see the relative size and exact counts of three possible outcomes of any referential relationship: joins (values are present in both EMPLOYEES and JOBS), orphans (values present in EMPLOYEES and not present in JOBS), and childless (values present in JOBSand not present in EMPLOYEES).

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Functional Dependency Analysis

Using functional dependency analysis, you can find out which attribute in a relation is determined by or dependent on which other attributes.




Pattern Domain

Orphans Childless


Functional Dependency AnalysisYou have completed two types of analysis: attribute analysis and referential analysis. Now you learn about functional dependency analysis, which is the last type of analysis that data profiling can perform. Using functional dependency analysis, you can find out which attribute in a relation is determined by or dependent on which other attributes.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Performing Functional Dependency Analysis

1

2

Performing Functional Dependency Analysis You find out 100-percent dependencies in the EMPLOYEES table by performing the following steps:

1. In the Profile Results Canvas, click the Functional Dependency tab.2. Select “Only 100% dependencies” from the Show drop-down list.

Observe that the DEPARTMENT_NAME column in the EMPLOYEES table depends on the DEPARTMENT_ID column. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Summary

In this lesson, you should have learned how to:• Create a data profile• Profile the data• View and analyze profile results

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 4-2: View and Analyze the Profile Results

This practice covers the following topics:• Viewing the profile results• Analyzing profile results

Practice 4-2: View and Analyze the Profile ResultsIn this practice, you view and analyze the profile that you created.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y



Defining Staging Metadataand Mapping Tables

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Objectives

After completing this lesson, you should be able to do the following:• Create a target module• Add a staging table to a staging area warehouse

module• Define mappings between source objects and

staging table columns

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Purpose of a Staging Area

• A staging area is a common platform.• Staging tables share a common database.• Staging tables can identify data with a point in

time.

Data marts/Warehouse

Staging area

Sources

Relationalsystems

Flat files

Purpose of a Staging AreaStaging tables are exact one-to-one copies of source tables. No heavy transformation is performed; they are primarily used for data movement. Because foreign keys are not necessary for staging tables, staging tables are populated without them. Staging tables are temporary tables that are meant to be overwritten.

• A staging area is a common platform to address:- Different topologies- Different operational systems- Multiple networks- Multiple protocols- Multiple sources

• Staging tables share a common database engine that can be tuned for data movement and transformation performance.

• Staging tables often use time-stamp fields to identify data with a point in time.Note: Staging tables and enterprise models are optional warehousing components. The needs and constraints that are unique to each warehousing situation dictate the appropriateness of using a staging area.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Defining a Staging AreaWarehouse Module

Defining a Staging Area Warehouse ModuleIn the lesson titled “Defining Source Metadata,” you created two source modules (HR and FILE_SOURCE) to define the metadata for your relational and flat file sources. Next, you learn how to create a target module and add staging table metadata to the warehouse module that you created. A warehouse module can contain metadata for a combination of the following objects:

• Mappings• Tables• Cubes• Dimensions• External tables• Views

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y












8. Execute or run the mappings.9. View the data.

Course Progress ReportSo far, you have defined the source module, imported the metadata, and profiled the source data. Now you create the staging area metadata.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating the Target User

Save or revert your changes before creating a user

Creating the Target UserDesigning the target system is where the real design work begins. Source modules hold metadata describing source systems from which you extract data. Target modules hold metadata describing your target data warehouse or data marts. Every target module must be mapped to a target user schema. Make sure that the target module references this target schema by assigning an appropriate location.To create the target user, ensure that you have logged in to Oracle Warehouse Builder (also called as Warehouse Builder or OWB) as the repository owner, only then you see the Security node in the Global Explorer panel.Note: You are prompted to save or revert your changes before creating a new user. To create the target user, perform the following steps:

1. In the Design Center, in the Global Explorer panel, expand the Security node.2. Right-click the Users node, and select New. If you have not saved your work, the

Warehouse Builder Error dialog box appears. Click OK in the error window where you are asked to save or revert changes before registering a new user and perform step 1.

3. Click Next on the Welcome page of the Create User Wizard.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create User Wizard: Select DB User to Register

Create User Wizard: Select DB User to RegisterOn the “Select DB user to register” page of the Create User Wizard, you can select from the available list of database users or create a new user that will automatically be registered as the Warehouse Builder target user. To create a new target user, perform the following steps:

1. Click Create DB User. The Create Database User window is displayed.2. In the Create Database User window, enter the following details:• SYSDBA name: sys (To be able to create a new target user, you need to use an

account that has SYSDBA privileges.)• SYSDBA password: (Enter the password for the SYS account.)• New DB user:

- Name: STAGING_USER- Password: STAGING_USER

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create User Wizard: Check Useras Target Schema

Create User Wizard: Check User as Target SchemaOn the “Check user as target schema” page, ensure that the “Used as target schema?” check box is selected. This indicates that the STAGING_USER user will be used as a target schema. Note: On the successful completion of the database user creation, check for the following:

• In the Design Center, in the Global Explorer panel, under Security > Users, a user named STAGING_USER is created for you.

• In the Design Center, in the Connection Explorer panel, under Locations > Databases > Oracle, a location named STAGING_USER_LOCATION is created for you. This location name can be used when you create the warehouse module.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating the Warehouse Target Module

Creating the Warehouse Target ModuleAfter having successfully created the target user, you are now ready to create the target module.To create a target module, perform the following steps:

1. In the Design Center, in the Project Explorer, expand CLASS_PROJECT > Databases.2. Right-click Oracle, and select New. The Create Module Wizard is displayed.

The Welcome page lists the steps that guide you through the module creation process. Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y





Create Module Wizard: Name and DescriptionOn the Name and Description page, enter details for the following:

• A module name• A module status (Development, Quality Assurance, or Production)

- Accept the default module status. The module status (Development, Quality Assurance, or Production) is only for documentation purposes and does not affect code generation.

• The module type- Choose Warehouse Target because you are creating the warehouse module.

• An optional descriptionO

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly





Create Module Wizard: Connection InformationOn the Connection Information page, from the Location drop-down box, select an existing STAGING_USER_LOCATION. The connection details are filled in automatically. Note: The target module does not need to import metadata; therefore, leave the “Import after finish” check box deselected. Expand CLASS_PROJECT > Databases > Oracle. Your target module is created, and you see the STAGING_AREA target module in the Project Explorer. For this course, you first created a target user (STAGING_USER) and then created a target module (STAGING_AREA). Defining the target user is not a compulsory step for creating a target module. You can use an existing database user to create a target schema.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




What Are External Tables?

Flat file Staging area Data mart

Flat file Data martExternal table

SQL*Loader PL/SQL

PL/SQL

Avoids this extra step

Geography.CSVGEOG_Ext

What Are External Tables?External tables represent data from nonrelational sources in a relational table format. An external table is a read-only table that is associated with a single record type in external data, such as with a flat file. External tables enable you to access flat files as though you were accessing an Oracle database table. With external tables, you can directly query flat files from the Oracle database and also query, join, transform, and constrain flat files. Oracle9i introduced external tables, a new concept that enables you to directly query flat files from the Oracle database and gives you a unique opportunity to query, join, transform, and constrain flat files. In Oracle8i (and earlier releases), the only way to load flat files into Oracle databases was to use Oracle SQL*Loader. You can define external tables on top of flat file structures and deploy the external tables to the database. In this lesson, you learn how to use external tables in mappings.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating an External Table

Creating an External TableNow you learn how to create an external table. External tables are defined on top of the flat file structures.To create an external table, perform the following steps:

1. In the Project Explorer, expand CLASS_PROJECT. Expand Databases > Oracle > STAGING_AREA.

2. Right-click External Tables, and select New. Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create External Table: Name and Description

Create External Table: Name and DescriptionOn the Name and Description page, perform the following steps:

1. Enter a name for the external table.2. Enter an optional description for the external table.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create External Table: File Selection

Create External Table: File SelectionOn the File Selection page, select the file containing the metadata for the external table.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create External Table: Locations

Create External Table: LocationsOn the Locations page, select the location that is used by the external table.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Configuring External Tables

Configuring External TablesUsing the Configuration Properties window, you configure the physical file system details for the external table:

1. In the Project Explorer, navigate to the module where you created the external table.2. Expand the External Tables node.3. Right-click the external table (in this example, GEOG_EXT), and select Configure.4. In the Configuration Properties window, right-click Data Files, and select Create

Datafile.5. On the right, enter the name and extension of the data file; the file name should be the

same name along with the extension as that of your flat file.6. Select the location of this data file for the external table.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 5-1: Overview

This practice covers the following topics:• Creating a target user• Creating a staging warehouse module• Creating an external table

Practice 5-1: OverviewIn this practice, you create a target user that is your actual data warehouse schema. You then create the staging warehouse module and an external table.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 5-1: Create an External Table

Location

STAGING_USER_LOCATIONUsername: STAGING_USERPassword: STAGING_USERHost: Your host name/LOCALHOSTSID: Your SID name/orcl

Target module

STAGING_AREA

External table created

GEOG_EXT

Target schema

STAGING_USER

You create the following objects:

Practice 5-1: Create an External TableIn this practice, you create the STAGING_AREA target module. The schema that is associated with this module is the STAGING_USER target user and the location associated with this module is STAGING_USER_LOCATION that already exists.You then create an external table that will be in the STAGING_AREA module. The external table as of now consists of only the metadata. This table does not have any data now. After completing practice 5-2, you will be able to view the data in the GEOG_EXT external table that you created.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




OWB Mapping

• Extract, transform, and load (ETL) involves the movement and transformation of data from your sources to your targets.

• Use OWB mappings to specify which source data objects provide data to which target data objects.

• Mapping definitions reside in target modules.

OWB MappingsYou learn how to create mappings to extract data from sources, transform it, and load it into targets.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Metadata to Data





Now you can view the data.

5.

Metadata to DataIn the lesson titled “Defining Source Metadata,” you created the source module and imported the metadata. In this lesson, you use the metadata to define a mapping, and deploy and execute the mapping to view the data that is loaded into the target object.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Building a Mapping

Identify the target module.

Create a mapping.

Connect operators using connection lines.

Generate the mapping.

Add operators, and specify the source and target.

Deploy the mapping.

Execute the mapping.

Building a MappingThe steps used for building a mapping are listed in the slide. Note the following:

• The target module used for this lesson is STAGING_AREA.• The mapping that you create will be named LOAD_STG_GEOG.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Designing the LOAD_STG_GEOG Mapping

Designing the LOAD_STG_GEOG MappingIdentify the target warehouse module in which you create mappings.To create a mapping, perform the following steps:

1. Navigate to the warehouse module—for this example, the staging module (STAGING_AREA)—where you want to create the mapping.

2. Right-click the Mappings node, and select New.3. In the Create Mapping dialog box, enter the name LOAD_STG_GEOG as the mapping

name. Optionally, enter a description. Click OK.The Mapping Editor is launched.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




OWB Mapping Editor

Toolbar

Menu bar

Canvas

Indicator bar

OWB Mapping EditorOWB Mapping Editor is an object-oriented, visual modeling tool for viewing and designing your data warehouse mappings between source and warehouse objects. In the Mapping Editor, you see a menu bar, multiple toolbars, a canvas, an indicator bar, and multiple windows.PaletteThe Palette displays icons that you can drag onto the canvas. Expand the drop-down list to see the various options.Mapping Editor WindowsExplorer: The Explorer has two tabs: Available Objects and Selected Objects. Click the Available Objects tab to see the objects that you can view or edit on the canvas. Click the Selected Objects tab to see a tree listing of all the activities on the canvas and their parameters.Properties: This displays the properties for the mapping, its operators, and attributes in the operators.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Mapping Editor User Interface

Auto layout

Fit in window

Mapping Editor User InterfaceIn the Mapping Editor user interface, make yourself familiar with the following:

• The icons used for each operator type are consistent in OWB. For example, the icon for a table operator (in the Mapping Editor canvas, Palette, and Explorer) is the same. This should make identifying mapping operators easier especially for more complicated mappings.

• Each operator on the canvas can be minimized, maximized, and displayed as an icon. This helps to make things easier to visualize in mappings. Click the Maximize icon to maximize the operator. Click the Restore icon to restore the operator to the original size. Click the Icon icon to get an icon image of the operator, and double-click the icon to get back to the normal view.

• Commonly used options:- Auto Layout: To do an automatic layout of the objects in the Mapping Editor

canvas, from the menu, select View > Auto Layout. - Fit in Window: On the toolbar, click the “fit in window” icon to be able to see

the complete mapping. You can also get a panoramic view of the canvas by selecting Birds Eye View from the Window menu.

• Within each operator on the canvas, you see the name and data type of each attribute to make mapping easier. Data type is expressed in symbols (for example, abc means varchar2).

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Building a Mapping


Create a mapping.

Connect operators by using connection lines.



Deploy the mapping.


Building a MappingYou learn how to create a simple mapping that uses the external table as the source and create a staging table in the staging area warehouse module.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




1

Choosing the External Table

2

Choosing the External TableThere are two ways of choosing the external table.Using ExplorerUse this option if objects exist in the Project Explorer in the Design Center and will appear on the Available Objects tabbed page.

• From the Explorer window on the left, click the Available Objects tab.• Navigate to the warehouse module where the external table resides.• Expand the External Tables node.• Drag the external table acting as the source onto the canvas.

Using PaletteUse this option when you have to create a new object.• From the Palette, drag the external table operator onto the canvas.• In the Add External Table Operator window, select “Select from existing repository

objects and bind.” In this example, the GEOG_EXT external table is selected.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Drag the table operator onto the canvas.

Creating a Staging Table

Creating a Staging TableIn this example, the target mapping table represents the staging table. From the Palette, drag the table operator onto the canvas to the right of the external table operator. In the Add Table Operator dialog box, select “Create unbound operator with no attributes.” Enter a name for the table operator. Warehouse Builder displays the operator on the canvas without any attributes. The create unbound operator with no attributes enables you to use the Mapping Editor to define a new repository object, such as a new staging area table or a new target table. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Adding an Attribute

New attribute

Adding an AttributeYou can add attributes to the mapping table. The example used here is only to demonstrate how to add additional attributes.

1. Right-click the STG_GEOG table, and select Open Details.2. In the Table Editor window, click the Input/Output tab. You see the list of existing

attributes.3. Click Add.4. In the Attribute Name field, rename INOUT1 as LOAD_DATE. Change the data type to

DATE, and click OK.O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Using a Constant Operator

Using a Constant OperatorYou use the constant operator to define constant values. The constant operator produces a single output group that can contain one or more constant attributes. Adding a Constant Operator onto the CanvasIn the Mapping Editor, from the Palette panel, select All from the drop-down list (if not already selected). Drag the constant operator onto the canvas. Adding Attributes to the Constant OperatorRight-click the header area of the constant operator. Select Open Details. Click the Output Attributes tab. Click Add.Rename the attribute name and the data type to match your requirement.Adding a Value for the AttributeOn the canvas of the Mapping Editor, select the attribute for which you want to specify a value. In the Attribute Properties panel, click Expression and click (the three dotted button).The Expression Editor is launched. The Expression Editor is discussed on the following page.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Using the Expression Builder to Definea Constant Operator

Using the Expression Builder to Define a Constant OperatorExpression Builder provides an easy-to-use editor that enables quick construction of expression by using a drag-and-drop interface. These expressions can then be verified to be syntactically and semantically correct before leaving the editor. TransformationsClick the Transformations tab. Expand Public > Predefined > Date, and select SYSDATE, which is a predefined transformation.ValidatingAfter defining the constant value, it is a good practice to validate the expression you built.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Using a Filter Operator

1

2

3

Using a Filter OperatorYou can conditionally filter out rows by using the Filter operator. The Filter operator filters data from a source to a target by placing a WHERE clause in the code that is represented by the mapping. You create many more filters in this same mapping with different filter conditions.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Using the Expression Builder to Definea Filter Condition

Using the Expression Builder to Define a Filter ConditionIn the previous slide, you saw how to use the Expression Builder to define a constant value. In this slide, you use the Expression Builder to define a filter condition.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Using a Joiner

Using a JoinerYou use the Joiner operator to join multiple row sets from different sources and produce a single output row set.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Key Lookup Operator

Key Lookup OperatorBy using the Key Lookup operator, you can perform a search for data from a lookup object, such as a table, view, fact, or dimension. The key that you look up can be any unique value. It does not need to be a primary or unique key, as defined in an RDBMS.The Key Lookup operator reads data from a lookup table by using the key input that you supply and finds the matching rows. This operator returns a row for each input key.

1. Drag a key lookup operator from the Palette onto the canvas.2. The Key Lookup Wizard guides you through the creation of a Key Lookup operator.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Key Lookup Condition

Key Lookup ConditionThe key lookup condition is based on the source inputs. This condition is used to look up a value in the bound table. If the condition is not met, the default value expression is returned.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Set Operation Operator

Set Operation OperatorWith the Set Operation operator, you can use set operations in a mapping. You can specify UNION, UNION ALL, INTERSECT, or MINUS. The default is UNION. Mapping attributes to a Set Operation operator input group creates corresponding attributes with the same name and data type in the Set Operation output group.To execute the Set Operation operator:

• All sets must have the same number of attributes• The data types of corresponding attributes must match

In the example in the slide, the UNION ALL set operator is used for the two tables.Attribute Order Is ImportantCorresponding attributes are determined by the order of the attributes within an input group. For example, attribute 1 in input group 1 corresponds to attribute 1 in input group 2.Apply the set operation in top-down order. The order of the input groups determines the execution order of the set operation. This order affects only the minus operation. For example, A minus B is not the same as B minus A. The order of the attributes within an input group determines the structure of a set. For example, {empno, ename} is not the same as {ename, empno}.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Building a Mapping


Create a mapping.




Deploy the mapping.


Building a MappingYou connect the source operators to the target operators by using connection lines.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Mapping Source Columns to the Target

Individually mappingcolumns to targets

Automatically mappinggroups of attributes

Mapping Source Columns to the TargetManually Mapping Individual AttributesYou can individually map the source attributes to the target. Do this by dragging a line from attributes in the source to the INOUTGRP1 group of the target table. If the target tables do not have any attributes, a new attribute with the same name is created and the connection line is also created. If the target tables already have the attributes, you can do a one-to-one mapping of attributes by dragging a connection line from the source attribute to the attribute in the target.Automatically Mapping Groups of AttributesIn other cases, you often want to map all source attributes to a target. In such cases, you can drag a group of attributes in one quick step from the source to the target. You drag a line from the group’s label (OUTGRP1) in the flat file source object to the group’s label (INOUTGRP1) in the target mapping table.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Using the Create and Bind Option to Create the Repository Table

Using the Create and Bind Option to Create the Repository TableThe STG_GEOG table exists in the mapping as a mapping table with attributes that are mapped from the external table. However, this new table does not exist as an OWB repository table yet. To create the repository table, right-click the STG_GEOG title bar, and select Create And Bind.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Setting Load Typeto TRUNCATE/INSERT

Setting Load Type to TRUNCATE/INSERTBecause staging tables are temporary tables for which history need not be retained, it is appropriate to change the loading type from the default value of INSERT to TRUNCATE/INSERT.Access the mapping table properties from the Property Inspector panel in the Mapping Editor. In the Loading Type field, select TRUNCATE/INSERT from the drop-down list.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Synchronizing Operatorsand Repository Objects

Mapping operator

Synchronize froman operator to

a repository object.

Synchronize froma repository object

to an operator.

Synchronizing Operators and Repository ObjectsRepository Objects Versus Operators in MappingsMapping operators are different from repository objects. Objects in the repository are referred to as repository objects (for example, repository table and repository views). Operators in the mapping are referred to as table operators, view operators, and so on. Synchronizing When you reimport a new metadata definition for the repository table, you may want to propagate those changes to the table operator in the mapping. Conversely, because you make changes to the table operator in a mapping, you may want to propagate those changes back to its associated repository table. You can accomplish these tasks by a process known as synchronizing. In Warehouse Builder, you can synchronize manually from within the Mapping Editor. From the Synchronize dialog box, select one of the following:Synchronize from a repository object to an operator: In the Mapping Editor, you synchronize from a repository object to its associated operator to propagate changes made in the repository object to the operator. Synchronize from an operator to a repository object: You choose this option when you have made changes to an operator in a mapping and want to propagate those changes back to a repository object.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Building a Mapping


Create a mapping.




Deploy the mapping.


Building a MappingAfter designing the mapping, you use OWB to generate the mapping.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Validating the Mapping

Validating the MappingValidation is the process of verifying metadata definitions and configuration parameters. These definitions must be valid before you proceed to generation and deployment of scripts. Warehouse Builder runs a series of validation tests to ensure that data object definitions are complete and that scripts can be generated and deployed. While in the Mapping Editor, you can validate your definitions by selecting Validate from the Mapping menu.Validation detects:

• Data type mismatches• Missing parameters• Incomplete mappings• Invalid objects• Invalid references

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Generating the Mapping

Generating the Mapping You generate OWB mappings to implement the SQL code that performs the data manipulation language (DML) and data definition language (DDL) commands that are necessary to move the data from the sources to the mapped targets. To generate the mapping code from the Mapping Editor, from the Mapping menu, select Generate. Alternatively, you can generate the mapping code from the Design Center. In the Project Explorer, right-click the mapping, and select Generate. Monitor the progress on the Design Center status bar.Mappings with Relational Sources Produce PL/SQL CodeThe mapping, with a relational table as the source, results in PL/SQL code with typical INSERT, INTO, and SELECT statements. Mappings with Flat File Sources Generate Code for SQL*Loader Control FilesFor a mapping that extracts records from a flat file and loads them as rows into a target table, the generated code results in a SQL*Loader control file.The code in this example’s mapping differs from the mapping code for the flat file mappings. The flat file mappings produce code that results in SQL*Plus control files.Inspecting Mapping Code from the Mapping EditorIn the Mapping Editor, select Window > Generation Results.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Building a Mapping


Create a mapping.




Deploy the mapping.


Building a MappingAfter generating the mapping, you deploy it. Deployment is the process of creating physical objects in a target location from the logical objects in a Warehouse Builder repository.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Deploying a Mapping

Before you deploy a mapping, you must perform the following steps:1. Deploy the

source object used in the mapping.

2. Deploy the target object used in the mapping.

3. Deploy the mapping.

1

2

3

Deploying a MappingYou have designed and configured the logical definitions of a staging system. Now you can deploy and create the physical instance of the staging system. Deployment is the process of creating a target system from the logical design or model. You first deploy all the relational and dimensional objects you created, and also deploy the ETL mappings that you designed. In the lesson titled “Deploying, Loading, and Viewing Data,” you learn more about deploying objects. To deploy an object, perform the following steps:

1. In the Project Explorer, right-click the object, and select Deploy. (You can do this only if you have validated and generated the object. Otherwise, right-click the object, and select Validate. After successfully validating the object, right-click the object, and select Generate.)

2. You see the progress of the operation on the Design Center status bar at the bottom.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Building a Mapping


Create a mapping.




Deploy the mapping.


Building a MappingWhen you execute the mappings, the mapping data is extracted from the source locations, transformed as specified in the mappings, and loaded into objects in the target location.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Executing a Mapping

Executing a MappingNow that you have deployed the mapping, the final step is to execute the mapping to populate the staging target table.In the Design Center, right-click the mapping, and select Start. The execution process completes successfully. In the Design Center, right-click the table, and select Data. If loading is successful, you see the data in the Data Viewer. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Metadata to Data





Now you can view the data.

5.

Metadata to DataAfter creating the mapping, and deploying and executing it, you are ready to view the results of your work.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Viewing the Data Using Data Viewer

The result of your work!

Viewing the Data Using Data ViewerThe Data Viewer window shows the rows that were inserted into the STG_GEOG staging table. Right-click the STG_GEOG table, and select Data. The Data Viewer is launched, and it displays the table data.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Pluggable Mappings

Pluggable mapping

Mapping

Pluggablemappinginputs

Pluggablemappingoutputs

Mapping containing pluggable mapping as operator

Pluggable mapping

Pluggable mappings are

like functions in PL/SQL.

Pluggable MappingsAfter you design a mapping, you can reuse its flow in other mappings by creating a nested mapping that contains the portion of the flow you want to reuse. A nested mapping is a reusable mapping component that represents a flow of operators. When defined, it appears as a single mapping component, as shown in the slide. Input and Output RowsetsLike any operator, the nested mapping has input and output attributes that enable you to connect it to other operators in various mappings. From the technical perspective, you can conceive a nested mapping as an object that accepts certain input rowsets from the upstream mapping graph, performs certain arbitrary transformations, and produces certain output rowsets for the downstream mapping graph.Equivalent to Functions in Programming LanguagesA nested mapping is a mapping construct for encapsulating certain data transformation logic. Naturally, nested mappings can be nested and can encapsulate transformation logic in other nested mappings. The nested mapping construct in mappings is analogous to the function construct in any programming language.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Advantages of Pluggable Mappings

• Pluggable mappings are in essence reusable building blocks for a mapping.

• Users define reusable mapping logic as a pluggable mapping, and then deploy it in one or more of their mapping designs, or share it with other users.

Business benefits:• Hide complexity• Reuse combinations of

complex mapping constructs

Advantages of Pluggable MappingsBusiness PerspectiveMappings in OWB are usually complex with many stage components interconnected with each other. From the business perspective, the user would want to group certain parts of the mapping into a container with one of the following in mind:

• To encapsulate complex or less important mapping logic into a single unit for better comprehension. This gives the user a way to break down a mapping into logical subunits when the mapping is being designed.

• To reuse part of the mapping logic within the same mapping or across multiple mappings. This gives the user a way to build a library of common mapping logic for later use in his or her design process.

Business Value• Hide complexity: An example is an API that loads a dimension• Reusability: Informatica (which calls pluggable mappings maplets) stresses this as the

most important reason. You can draw a box around an object and declare it public. You design once, and take pieces out of it that can be reused. It works like a function in PL/SQL. It is like a function that converts euros to dollars.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Example of a Pluggable Mapping

Pluggable mapping expanded within mapping

Parent mapping

Input and outputsignatureoperators

Example of a Pluggable MappingInput and Output SignaturesThe signatures of a pluggable mapping describe the structure of the input rowsets (a set of rows with the same cardinality) and the output rowsets of the pluggable mapping. The signatures are expressed as operators in the pluggable mapping, with the input and input/output attribute groups (if needed) forming the input signature component, and the output and input/output attribute groups (if needed) forming the output signature component. The structure of each rowset in the signature is represented by an attribute group of an appropriate direction with attributes of the corresponding data types. Child GraphIn the Mapping Editor canvas of a mapping that contains a pluggable mapping, you can drill down to an expanded view of the pluggable mapping. (Click Child Graph on the toolbar.) In the example in the slide, the pluggable mapping does not contain any output, so there are no lines connecting to the output signature operator. In other situations, you can connect some of the operators in the pluggable mapping to the output signature so that the operatorscan be used as input to any downstream operators in the parent mapping.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Target Load Ordering

• Allows loading related targetsin a single mapping in order

• Determines target load order based on foreign keys first, to load master before detail

Target Load OrderingIf you were to load ADDRESS first, and the CUSTOMERS data did not exist for it, then you would receive numerous errors. You want the CUSTOMERS data to load first.If you have a mapping with multiple targets, ensure that Warehouse Builder loads the targets in a specific order. This is the case when a column in one target derives its data from another target. In a mapping with multiple targets, you can generate code that defines an order for loading the targets by using the mapping property, Target Load Order.When you design a PL/SQL mapping with multiple targets, Warehouse Builder calculates a default ordering for loading the targets on the basis of the key relationship (Primary Key > Foreign Key).

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Overriding the Default Load Order

You can change the order usingthe up and down arrow buttons.

Click the mapping canvas to see Target Load Order in the inspector.

Overriding the Default Load OrderDefault OrderIf you define foreign key relationships between targets, Warehouse Builder creates a default order that loads the parent and then the child. If you do not create foreign key relationships or if a target table has a recursive relationship, then Warehouse Builder assigns a random ordering as the default. You can override the default load ordering by setting the Target Load Order property. Overriding the Default OrderYou can override the default load ordering by setting the Target Load Order property.To change the loading order, select a target and use the arrow buttons on the right to move the target up or down in the list.Reset to DefaultUse the Reset to Default button to instruct Warehouse Builder to recalculate the target loading order. You may want to recalculate if you made an error while reordering the targets or if you assigned an order and later changed the mapping design such that the original order became invalid.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Summary

In this lesson, you should have learned how to:• Define a staging area target module• Add a staging table to a staging area target

module• Create a simple mapping from source objects to a

target

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 5-2: Create a Simple Mapping from Source Objects to the Target

This practice covers designing a mapping from source objects to a target.

Practice 5-2: Create a Simple Mapping from Source Objects to the TargetIn this practice, you learn how to create a simple mapping from source objects to a target.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y



Deriving Data Rules and Running Correction Mappings

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Objectives

After completing this lesson, you should be able to do the following:• Derive data rules• Create a correction• Run the generated correction mappings

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y













9. View the data.

Course Progress ReportIn this lesson, you derive data rules from the results of the data profiling done in the lesson titled “Ensuring Data Quality Using Data Profiling” of this course. You also run the generated correction mapping.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Lesson Progress Report

• Deriving data rules• Creating corrections• Deploying and running the correction mappings

Lesson Progress ReportWhat do you do in this lesson?Data profiling does not stop at analyzing the profiled data; in fact, you can take it a step further by being able to derive data rules from the results of data profiling. In the lesson titled “Ensuring Data Quality Using Data Profiling,” you discovered that domain values for JOB_ID were only 98 % compliant. The user also had a question: What does one do after finding that there were some noncompliant records? In this lesson, you derive data rules for the JOB_ID domain values anomaly.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Data Rules

• Data rules validate the single “known”: “Which records comply with this particular pattern?”

• One way of creating data rules is by deriving them from profile results.

• One way of using data rules is creating correction.

Data RulesA data rule is a user-entered or process-derived expression that determines the legal data within a data object or legal relationships between data objects. For example, Gender is “M” or “F.”

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Deriving Data Rules

A data rule is an expression that determines the set of legal data that can be stored within a data object.

1

2

3

Deriving Data RulesTo derive a data rule, perform the following steps:In the Project Explorer, expand Data Profiles, and double-click HR_DP. The Data Profile Manager opens and displays the data profile.

1. Click the Domain tab. 2. Scroll down to the JOB_ID row. Select the values in the Found Domain column.

Note: The symbol in the Found Domain column indicates that you can derive a data rule from the finding.

3. On the lower-right portion of the Profile Results Canvas, click Derive Rule.O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Derive Data Rule Wizard: Welcome

Derive Data Rule Wizard: WelcomeThe Derive Data Rule Wizard is launched. This page lists the steps that guide you through the derivation of a data rule process.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Derive Data Rule Wizard:Name and Description

Derive Data Rule Wizard: Name and DescriptionOn the Derive Data Rule – Step 1 of 2: Name and Description page, accept the default namefor the data rule or specify a name according to your requirements.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Derive Data Rule Wizard: Define Rule

Derive Data Rule Wizard: Define RuleOn the Derive Data Rule – Step 2 of 2: Define Rule page, you see the list of values that are deemed to be compliant with the domain automatically populated for you (SH_CLERK, ST_CLERK, and so on).Note: You can do one of the following:

• Move values from the “Additional discovered values” list to the “Selected values” list.• Enter new values into the “Selected values” list, if you want some domain values that

are not present in the current data set.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Derive Data Rule Wizard: Summary

Derive Data Rule Wizard: SummaryReview the Summary page, and click Finish.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Examining the Data Rule Panel

Examining the Data Rule PanelExamine the Data Rule Panel in the lower portion of the window. The created data rule JOB_ID_RULE_1 is displayed with its details, such as the type (Domain List). Note how the derivable symbol changed to the derived symbol in the Found Domain column of the JOB_ID row. The newly derived rule now also appears on the console tree. This is because the data rules are reusable—that is, they can be attached or “bound” to any object. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly





See how “data profiling is integrated into ETL.”• Deriving data rules• Creating corrections• Deploying and running the correction mappings

Lesson Progress ReportWhat do you do with the data rules that you just derived? In this lesson, you use a data rule to create a correction. A correction:

• Creates a corrected table in the target module• Creates a mapping to move the data from the profiled source to the corrected target.

This mapping enforces your data rule and corrects the records that do not comply with the data rule.

All this is done automatically: You do not need to enter any code in the Mapping Editor.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating Corrections Using the Create Correction Wizard

Creating Corrections Using the Create Correction WizardNow, using the Create Correction Wizard, you create a correction for the data rule. To invoke the wizard, in the Data Profile Manager, from the Profile menu, select Create Correction. The Create Correction Wizard is launched.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Correction Wizard: Select Target Module

Create Correction Wizard: Select Target ModuleOn the Select Target Module page, you can:

• Create a new target module• Select an existing module

The data corrections and corrected tables are placed in the target module that you specify.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Correction Wizard: Select Objects

Create Correction Wizard: Select ObjectsOn the Select Objects page, you select the objects you want to correct. From the Available list, select EMPLOYEES from the HR node and move it to the Selected list.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Correction Wizard:Select Data Rules

Create Correction Wizard: Select Data RulesOn the Create Correction – Step 3 of 7: Select Data Rules page, the objects you selected on the previous page appear organized into a tree by modules on the left side. The available derived rule appears on the right side and is already bound. Also, you can select the data rules that you want to be applied to each object selected for correction.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Correction Wizard:Verify and Accept Corrected Tables

Create Correction Wizard: Verify and Accept Corrected TablesA progress dialog box appears and displays the data rules as they are applied. You now see the definitions for the target tables that Oracle Warehouse Builder (OWB) generated. The structure of the EMPLOYEES table being created is the same as that of the source table that was profiled. On this page, select the objects you want to create in the corrected schema. For this case study, the EMPLOYEES table is already selected. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Create Correction Wizard: Constraints Tab

Create Correction Wizard: Constraints TabOn the “Create Correction – Step 4 of 6: Verify and Accept corrected tables” page, click the Constraints tab. You see the JOB_ID_RULE1_18 check constraint being created in the target table.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Correction Wizard:Choose Data Correction Actions

What do you do with records that do not comply with the data rule?

Create Correction Wizard: Choose Data Correction ActionsWhat do you do with records that do not comply with the data rule? You know that there were records with the misspelled values PU_CLIRK and SA_REPP that are not part of the domain now enforced by the data rule or the check constraint. Will those records be ignored and pushed out by the constraint? You have a choice. You now have an opportunity to choose a data correction action. If you choose Cleanse as the action, you can choose the cleanse strategy. Choose Cleanse for the action and Similarity Match for the cleanse strategy. Similarity Match finds the closest compliant value in the domain and replaces the noncompliant value with it.Click Finish to exit the correction wizard. The correction schema tables and mappings are created and added to the Design Center.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y





• Deriving data rules• Creating corrections• Deploying and running the correction mappings

Lesson Progress ReportOn the basis of the data profiling finding of the domain, you have:

• Derived a data rule to enforce the domain• Created a target table where the domain data rule is implemented with a check

constraint.• Created a correction action that attempts to correct the noncompliant records with

Similarity Match.After having worked with the wizards, see the results of your work in the following slides.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Examining the Correction Module

Examining the Correction ModuleIn the Project Explorer, expand Databases > Oracle > DP_TGT (the target module that you selected in step 2 of the Create Correction Wizard). You see that there is an EMPLOYEEStable and the M_EMPLOYEES mapping.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Examining the Generated Correction Mapping

Examining the Generated Correction MappingIn the Project Explorer, double-click M_EMPLOYEES to open the mapping in the Mapping Editor. On the toolbar, click the Autolayout icon.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Examining the Generated Correction Mapping

Examining the Generated Correction Mapping (continued)You are now looking at the submap that does the actual cleansing specified in the Create Correction Wizard (remember: Similarity Match). In the middle of this submap is the SIM_JOB_ID transformation that was generated as a function by the Create Correction Wizard. Close the mapping.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Examining the Transformations Node

Examining the Transformations NodeIn the Project Explorer, expand DP_TGT > Transformations > Functions. Double-click the SIM_JOB_ID function, and click the Implementation tab.You see code in this implementation, such as:s(1):= 'SH_CLERK'; s(2):= 'ST_CLERK'; s(3):= 'SA_REP'; s(4):= 'PU_CLERK'; s(5):= 'IT_PROG';…score := owb_match_merge.similarity(s(i), JOB_ID); The corrected tables and the mapping are regular OWB objects that can be edited, deployed, and executed.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Summary

In this lesson, you should have learned how to:• Derive data rules• Create corrections• Deploy and run the correction mappings

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 6-1: Deriving Data Rulesand Creating Correction Mappings

This practice covers the following topics:• Creating a data rule• Using the data rule to create a correction

Practice 6-1: Deriving Data Rules and Creating Correction MappingsIn this practice, you create a data rule that provides automation of action on the basis of the results of data profiling. You also learn how to use the data rule that you created to create a correction.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y



Defining a Relational Dimensional Model

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Objectives

After completing this lesson, you should be able to do the following:• Define dimensions and cubes • Navigate the Data Object Editor• Define ETL mappings to load the dimensions and

cubes

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y











7. Deploy the objects.


9. View the data.

Course Progress ReportOracle Warehouse Builder (also called as Warehouse Builder or OWB) provides an advanced relational and dimensional modeling environment. You can easily design, create, and manage a variety of database objects by using an intuitive user interface. This interface supports fast user entry of design details and provides an environment that enables the user to build warehouse schema designs through the use of diagrams and property sheets. In this lesson, you learn how to perform relational and dimensional modeling.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Lesson Scenario

Target module: SALES_WHSchema details: sales_wh/sales_wh

Created by learner

Precreated

LOAD_PRODUCTSLOAD_CHANNELS

LOAD_CUSTOMER

LOAD_PROMOTIONS

TIMES_MAP

LOAD_SALES

Mappings

SALES--------Cube

CHANNELS

TIMES

PRODUCTS

CUSTOMERS

PROMOTIONSDimensions

Lesson ScenarioThis lesson uses the SALES_WH target schema. The SALES_WH target module is created for you with two dimensions: • PROMOTIONS• CUSTOMERS

You learn how to create the following dimensional objects:The CHANNELS dimension by using the wizard The TIMES dimension by using the Time WizardThe PRODUCTS dimension by using the editorThe SALES cube by using the wizard When you create a time dimension by using the Time Wizard, OWB automatically creates a mapping for you. The precreated mappings for this course are LOAD_CHANNELS, LOAD_CUSTOMERS, LOAD_PROMOTIONS, LOAD_SALES, and TIMES_MAP.You create the LOAD_PRODUCTS mapping (mapping to load the PRODUCTS dimension).The appendix titled “Create the LOAD_SALES Mapping” has the guided steps to create the LOAD_SALES mapping (mapping to load the SALES cube).

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Classifying the Data

Descriptors Time

Dimensions

Metrics

Cubes

Classifying the DataTo group data so that it can be translated to a data model, the information set must be classified by subject. For example, product-related descriptors can form one group, and time descriptors (such as week, day, month, and fiscal year) can form another. These groups are descriptors of the business, or dimensions. The metrics, or measurements, of the business are grouped separately and are called cubes.Dimensions

• Dimensions are typically represented along the axes of existing reports.• Time is often generated by a tool and is a very important dimension.• Consider what your business needs are for the time dimension.

Cubes• A need or capability to summarize often identifies a cube.• A cube can be additive or partially additive across dimensions.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Dimension Tables

Dimension tables have the following characteristics:• They contain textual information that represents

the attributes of the business.• They contain relatively static data.

Dimension TablesDimensions are textual descriptions of the business. Dimension tables are typically smaller than cube tables. Dimension tables store the detailed attributes of business processes and transactions. Dimensions generally contain relatively static data; however, customer dimensions are updated more frequently.Dimensions Are Essential for AnalysisThe key to a powerful dimensional model lies in the richness of the dimension attributes because they determine how cubes can be analyzed. Dimensions can be considered as the entry point or edge into “cube space.” If you always name attributes in the users’ vocabulary, the dimension will document itself, and its expressive power will be apparent.Unlike in other database structures, dimensions are denormalized in a star schema

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Determining Granularity

Year?Quarter?

Month?Week?

Day?

Determining GranularityWhile grouping data, it is important also to think about the level of detail that can be used for analysis and for business decisions and actions. This level of detail is called granularity.The greater the level of detail (such as the account ID for a customer), the higher is the level of granularity. It is important to consider the granularity as you estimate the resources that are necessary to maintain the data warehouse.The Key QuestionWhat do your users really need for now and for the near future? Determine that and then design for one grain finer.Note: Remember that you can always aggregate upward, but you cannot disaggregate lower than the data that is stored in the data warehouse.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Dimensional Design Using OWB

Implementing a dimension consists of specifying how the dimension and

its data are physically stored.

Defining

Using wizard

Implementing

ROLAP

MOLAP

Deploying

Using editor

Dimensional Design Using OWBCreating dimensional objects includes three tasks:Defining Dimensional ObjectsWarehouse Builder provides you with two methods to define dimensions and cubes:

• Wizard: Use the wizard to create dimensional objects easily. The wizard creates a fully functional dimensional object, including the implementation objects that store the dimensional object data but with predefined defaults for certain features.

• Editor: Use the editor to create or edit dimensional objects. Use editors when you want to specify settings different from the default settings used by the wizards.

Implementing Dimensional ObjectsWarehouse Builder supports:

• Relational implementation of dimensional objects• Multidimensional implementation of dimensional objects

Deploying Dimensional ObjectsTo implement dimensional objects, you must deploy them. Deployment is covered in the lesson titled “Deploying, Loading, and Viewing Data.”

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Defining Dimensions

Using wizard Using editor

Defining DimensionsFor this course, you:

• Create the CHANNELS dimension by using the wizard• Create the PRODUCTS dimension by using the editor

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating a Dimension Using the Wizard

Creating a Dimension Using the WizardWhen you define dimensional objects, you describe the logical relationships that help store data in a more structured format. To create a dimension by using the wizard, perform the following steps:

1. In the Project Explorer, expand CLASS_PROJECT > Databases > Oracle > SALES_WH (the target module that has been precreated for you).

2. Right-click the Dimensions node, and select New > Using Wizard. The Welcome page of the Create Dimension Wizard is displayed. The Welcome page lists the steps to guide you through the dimension-creation process.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Dimension Wizard:Name and Description

Create Dimension Wizard: Name and DescriptionOn the Name and Description page, perform the following steps:

1. Enter a name for the dimension. 2. Optionally, enter a description.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Dimension Wizard: Storage Type

Create Dimension Wizard: Storage TypeOn the Storage Type page, you specify the type of storage for the dimension. The storage type determines how the dimension data is physically stored in the database. Select “Relational storage (ROLAP)” if you have high volumes of data combined with high refresh rates or if you have detailed high-volume data. In this course, you use the Relational storage (ROLAP) storage type. The Oracle Warehouse Builder 10g: Implementation Part 2course covers the multidimensional storage (MOLAP) type.Note: You select the storage type on the basis of the volume of the data stored at the lowest level of the entire cube and the refresh rate required. When you store dimension data in a relational form, OWB by default uses the star schema implementation method. Further in this lesson, you learn about the other methods (Snowflake and Manual) for implementing the dimension.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Dimension Wizard:Dimension Attributes

Create Dimension Wizard: Dimension AttributesOn the Dimension Attributes page, you define dimension attributes. By default, OWB creates three attributes for each dimension: ID, Name, and Description. You add more attributes, depending on your requirement. In the Identifier column, the drop-down list box has three values: Surrogate, Business, and Parent.

• A surrogate identifier uniquely identifies each-level record across all the levels of the dimension and is loaded from a sequence, as specified in the dimension key field.

• A business identifier is an attribute that is always picked from the natural key of the data source.

• A parent identifier is used to support value-based or parent-child hierarchies.If the attribute is a regular attribute (for example, none of the three), leave the field blank.In the Descriptor column, the dimension attributes marked as “Long description” and “Short description” are the ones used to display the dimension members in OLAP (online analytical processing)-aware query tools (Oracle Business Intelligence Discoverer and Oracle Business Intelligence Beans). Note: A dimension attribute is applicable to one or more levels in the dimension. On the next page of the wizard, you define the levels.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Dimension Wizard: Levels

• Specify levels in the default hierarchy (STANDARD). • The highest level appears at the top.

Use the arrow keys to change the order.

Create Dimension Wizard: LevelsThe Levels page defines the levels of aggregation in the dimension. List the levels in the dimension such that the parent levels appear above the child levels. When using the wizard, OWB creates a default hierarchy (STANDARD) that contains levels in the same order that you listed on the Levels page. Note: Use the editor to create multiple hierarchies.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Dimension Wizard: Level Attributes• By default, ID, NAME, and DESCRIPTION attributes

are selected for all levels.• For the lowest level, all the listed attributes are

selected.

Create Dimension Wizard: Level AttributesOn the Level Attributes page, you define the level attributes by selecting the dimension attributes that apply to the level. The Level Attributes page has two sections: Levels and Level Attributes. Note: By default, OWB selects the ID, Name, and Description attributes for all levels; for the lowest level, all the attributes are selected (in this example: ID, NAME, DESCRIPTION, and SOURCE_ID). Select a level in the Levels section. In the Level Attributes section, navigate to the attribute that needs to be selected. To the right of the attribute, select the Applicable check box to apply that attribute to the selected level. The following is the list to indicate the level attributes for each level. Levels Level AttributesTOTAL ID, NAME, DESCRIPTION, SOURCE_IDCLASS ID, NAME, DESCRIPTION, SOURCE_IDCHANNEL ID, NAME, DESCRIPTION, SOURCE_ID

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Dimension Wizard: Data Policy

Create Dimension Wizard: Data PolicyUsing the Data Policy page, you can define the type of slowly changing policy used by this dimension. For the slowly changing policy of the CHANNELS dimension, select “Type 1: Do not keep history.” This is the default selection. This is a normal dimension that stores no history.The other two types of slowly changing policies are covered in the lesson titled “Handling Slowly Changing Dimensions.” O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Create Dimension Wizard:Precreate Settings

Create Dimension Wizard: Precreate SettingsThe “Pre Create settings” page displays a summary of all the options selected on the previous pages of the Create Dimension Wizard. Note: Review this wizard page carefully. Examine the attributes, levels, hierarchies, storage type, and the slowly changing policy for the CHANNELS dimension.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Dimension Wizard: Dimension Creation Progress

Create Dimension Wizard: Dimension Creation ProgressThe “Create Dimension – Step 8 of 8: Dimension Creation Progress” page displays the progress of the dimension implementation that started on the previous page. The “Message log” section of this page provides information about the individual tasks completed during dimension implementation. Note: OWB creates the metadata for the following in the repository:

• The dimension object • The physical structures that store the dimension. For relational implementation, a

database table that stores the dimension data is created.• The database sequence used to generate the surrogate identifier for all the dimension

levelsWarehouse Builder creates these objects and performs autobinding. Binding is the process of relating the attributes of the dimensional object to the columns in the table that store its data. The advantage of using the wizard to create a dimension is that the objects are created and bound. You perform binding only for dimensional objects that have a relational implementation.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Configuring a Dimension

Configure the physical properties of a dimension.

Configuring a DimensionYou can configure the physical properties of a dimension in two ways:

• In the Project Explorer, right-click the name of the dimension you want to configure, and select Configure from the pop-up menu.

• In the Data Object Editor, use the Configuration window.You can configure the following dimension properties:Deployable: If it is selected, you can deploy the dimension.Deployment Options: Warehouse Builder provides three deployment options for dimensional objects:

• Deploy All: For relational implementation, the dimensional object is deployed to the Warehouse Builder repository and to the OLAP catalog.

• Deploy Data Objects only: The dimensional object is deployed only to the Warehouse Builder repository. You can select this option only for dimensional objects that have a relational implementation. If you deploy the objects using this option, you will not be able to view the loaded data through the Data Viewer because the Data Viewer uses the OLAP catalog metadata to show data.

• Deploy to Catalog only: The dimensional object is deployed to the OLAP catalog only. Using this option, you can view the loaded data in the dimensions and the cube in the Data Viewer.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 7-1: Create a DimensionUsing the Wizard

This practice covers creating the CHANNELS dimension by using the Create Dimension Wizard.

Practice 7-1: Create a Dimension Using the Wizard In this practice, you create one of the dimensions used in this course. You learn how to create a dimension by using the Create Dimension Wizard.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




About the Data Object Editor

Graphical view of dimension object: CHANNELSdimension

Details window

About the Data Object EditorThe Data Object Editor provides a canvas for creating and editing Oracle data objects.

• You can create relational (for example, tables), dimensional (for example, dimension and cubes), and intelligence objects.

• You can edit the objects by using the various tabs in the Details window that is located in the lower-right portion of the Data Object Editor.

Some of the windows in the Data Object Editor are:• Canvas: There are three tabs in the Canvas window: Relational, Dimensional, and

Business Definition.• Details: In this example, you opened the editor for a dimension. Therefore, the Details

window has tabs related to the object. The Dimension Details window has tabs for Name, Storage, Attributes, Levels, Hierarchies, SCD, and Data Viewer. Different object types (such as tables and cubes) have differently named tabs.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Detail View

Detail ViewOn the Canvas, you see three tabs: Relational, Dimensional, and Business Definition. In addition to these tabs, the Canvas allows for more tabs to be created. These tabs are displayed when you open an object (or more objects) in Detail View mode. A tab has the same name as the data object and displays the relationship between the data object and the object that it owns. Switching to Detail View ModeOn the Canvas, right-click the CHANNELS dimension, and select Detail View. You also see that the CHANNELS dimension is bound (autobound) to the CHANNELS table.A CHANNELS tab appears alongside the Relational, Dimensional and Business Definition tabs.For a dimensional object, this tab displays the bindings between the dimensional object and the data objects that store the dimensional object data. You must be in Detail View mode to perform manual binding. You learn more about types of binding later in this lesson.In the case of business intelligence objects, the dynamic tabs contain the item folder and its related tables.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating or Editing a Dimension Usingthe Data Object Editor

Creating or editing a dimension using the editor

• To use existing database tables or views to store the dimension data. This is also called manual binding.

• To use the snowflake or manual implementation methods. Star is the default implementation method for the ROLAP storage type.

• To create dimension roles• To use skip levels in a hierarchy

Creating a dimension using the wizard

• You can create dimension objects quickly.

• OWB provides default settings to the most commonly used values.

Versus

Creating or Editing a Dimension Using the Data Object EditorUsing wizards, you can create the dimension objects quickly. When you use the wizard, OWB provides default settings to the most commonly used values.After creating the dimension, say, you want to do any of the following tasks or more:

• Modifying the settings• Controlling all attributes and items in a dimension• Adding more attributes to the dimension• Adding a hierarchy• Changing the data policy

The Data Object Editor provides the ease of use to design any database or dimensional objects with a single editor. It also provides a canvas for creating and editing data object properties for relational data objects, such as tables, views, and materialized views, and for dimensional objects, such as dimensions and cubes. You can edit and configure data objects by using the tabs in the Details window located at the lower corner of the editor. In this lesson, you learn how to create a dimension by using the Data Object Editor.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating a Dimension Using the Editor

Advanced user: Using the editor to create a dimension

Using the editor,you can create a

new dimension in theData Object Editor, or

select an existingone to edit it.

Creating a Dimension Using the EditorYou learned how to create a dimension using the wizard. Using wizards, you can create dimensional objects quickly. OWB alternatively enables you to create or edit dimensional objects by using the Data Object Editor. In spite of the simple and easy-to-use wizard to create a dimension, advanced users may feel the need to create a dimension using the editor so that they can create the dimension according to their requirements.Creating a Dimension Using the Data Object EditorTo create a dimension using the Data Object Editor, perform the following steps:

1. In the Project Explorer, expand CLASS_PROJECT > Databases > Oracle > <Target Module>.

2. Right-click Dimensions, and select New > Using Editor. The Data Object Editor is launched.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Dimension Details: Name Tab

Dimension Details: Name TabCreating a Dimension

• Name and description - Enter a name for the dimension.- Optionally, enter a description.

• Dimension roles - Create a dimension role. Dimension role is explained in the next slide.

Editing a DimensionThe Create Dimension Wizard does not have a page to create a dimension role. If your requirement is to have a dimension role, create the dimension by using the editor. If an existing dimension needs to have a role, edit an existing dimension by using the editor and add a role.The next slide is about dimension roles.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating a Dimension Role

Creating a Dimension RoleA dimension role is an alias for a dimension. In a data warehouse, a cube can refer to the same dimension multiple times. This kind of multiple references to the same dimension may cause confusion. OWB provides you with an option of creating and using dimension roles. By using dimension roles, you can create an alias for each reference to the dimension. The same dimension now performs different dimension roles in the cube. You create roles for the dimension in the roles section. This example uses the CUSTOMERSdimension.Role DescriptionSHIP_TO_CUSTOMER Ship to address for the customerBILL_TO_CUSTOMER Address to bill the customerHere only the dimension role is created. Further in this lesson, when you are creating a cube, you learn how to assign these roles that you created to a dimension.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Dimension Details: Storage Tab

Dimension Details: Storage TabOn the Storage tabbed page, you specify the type of storage for the dimension. You can select from the following storage options:

• ROLAP: Relational StorageIn this course, you learn about only the ROLAP storage type. In the relational storage type, the dimension and its data are stored in a relational form in the database. For relational storage, there are three options to implement the dimension:

- Star: Implements the dimension by using a star schema. This means that the dimension is stored in a single database table or view.

- Snowflake: Implements the dimension by using a snowflake schema. In this type, the dimension data is stored in more database tables per level.

- Manual: You must explicitly bind the attributes from the dimension to the database object that stores their data.

• MOLAP: Multidimensional StorageIn MOLAP implementation, the dimensional object data is stored in an analytic workspace. The Oracle Warehouse Builder 10g: Implementation Part 2 course covers the MOLAP storage type.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Dimension Details: Attributes Tab

Dimension Details: Attributes TabCreating a DimensionOn the Attributes tabbed page, there are two sections: sequence and dimension attributes.

• Sequence: You need a sequence only for dimensions that have the storage type as ROLAP. The sequence is used to populate a dimension key column when loading data. Click Select to select a sequence object.Note: If you are using the wizard to create the dimension, then a sequence object is automatically created by OWB.

• Dimension attribute: A dimension attribute has a name and a data type. It is applicable to one or more levels in the dimension. The list of dimension attributes should include all the attributes that you may need for any levels in the dimension.

Editing a DimensionYou can:

• Add or delete attributes. (Ideally, do not delete the three default attributes created by OWB.) To delete an attribute, right-click the serial number next to the column name you want to delete.

• Select another sequence

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Dimension Details: Levels Tab

Dimension Details: Levels TabCreating a DimensionOn the Levels tabbed page, you see two sections: levels and level attributes.

• Levels: A dimension must contain at least one level. The levels in the dimensions must be created such that the parent levels appear above the child levels. This example has four levels: TOTAL, CATEGORY, SUBCATEGORY, and PRODUCT.

• Level Attributes: The level attributes section lists all the dimension attributes defined on the Attributes tabbed page. The values that you specify in this section are applicable to the level selected in the levels section. Observe that each level has an applicable set of attributes. For example, the TOTAL level implements all the dimension attributes except the last two (PACK_SIZE and LIST_PRICE), and the PRODUCT level implements all the dimension attributes as level attributes. Note: In the levels section, you add levels to the dimension. You do not add level attributes in the level attributes section; instead, you select those level attributes that are applicable to the selected level.

Editing a Dimension You can add more levels to the dimension in the levels section. You can also select or deselect level attributes implemented for a level.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Dimension Details: Hierarchies Tab

Dimension Details: Hierarchies TabA dimension hierarchy is a logical structure that uses ordered levels as a means of organizing data. A hierarchy describes parent-child relationships among a set of levels.Creating a HierarchyYou use the Hierarchies tab to create dimension hierarchies. The Hierarchies tab contains two sections:

• Hierarchies: Create a new hierarchy. Enter the hierarchy name. If a hierarchy is the default hierarchy, choose it from the default column.

• Levels: The levels section lists all the levels defined on the Levels tabbed page. “Skip to Level” represents the parent level of the level indicated by the Level field. Use this field to define skip-to-level hierarchies.

If you use the wizard to create a dimension, OWB creates only one hierarchy by default, namely, STANDARD.Editing a DimensionIf you use the wizard, OWB creates only one hierarchy (STANDARD) by default. If your requirement is to create additional hierarchies, use the editor to create more hierarchies.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Dimension Details: SCD Tab

Dimension Details: SCD TabA slowly changing dimension (SCD) is a dimension that stores and manages both current and historical data over time in a data warehouse. It is considered and implemented as one of the most critical extract, transform, and load (ETL) tasks in tracking the history of dimension records. The SCD tab displays the type of slowly changing policy for the dimension. SCD is covered in detail in the lesson titled “Handling Slowly Changing Dimensions.”Note: You can create a type 2 or type 3 SCD if you have specified the type of storage as ROLAP. Type 1 can be specified with both ROLAP and MOLAP storage types.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Relational Implementation: Star

Star implementation

Relational Implementation: StarIn a star schema implementation, OWB stores the dimension data in a single table or view. The table stores data for more than one dimension level; you specify a dimension key column in the table. The dimension key column is the primary key for the dimension and stores the surrogate identifier for each level. For the binding to occur, you must bind the dimension to the table (use the Auto Bind option).

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Relational Implementation: Snowflake

Relational Implementation: SnowflakeIn a snowflake schema implementation, OWB uses more than one table or view to store the dimension data. Separate tables store the data pertaining to each level in the dimension.Ralph Kimball on Snowflake ImplementationEvaluate whether you really want a snowflake. Ralph Kimball, considered a guru in data warehousing, recommends that in most cases, star schemas are a better solution. Although redundancy is reduced in a normalized snowflake, more joins are required. But Kimball proposes three cases where variations on a snowflake are not only acceptable, but are the keys to a successful design:

• Large customer dimensions where, say, 80 percent of the fact table measurements involve anonymous visitors about whom you collect little detail, and 20 percent involve reliably registered customers about whom you collect much detailed data by tracking many dimensions

• Financial product dimensions for banks, brokerage houses, and insurance companies because each of the individual products has a host of special attributes not shared by other products

• Multienterprise calendar dimensions because each organization has idiosyncratic fiscal periods, seasons, and holidays

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Binding

OWB provides two options for binding dimension attributes to the database columns that store their data:• Autobinding• Manual binding

BindingIf you use the wizard to create the dimension object, the wizard automatically binds the dimension object to the database tables that store the dimension. If you define the dimension structure using the editor, then you must specify the details about the database tables or views that store the dimension. OWB provides you with two options for binding dimension attributes to the database columns that store their data.

• Autobinding• Manual binding O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Autobinding

AutobindingWhen you perform autobinding, OWB automatically maps the attributes in the dimension to the database columns that store their data.To perform autobinding, ensure that the dimension object you want to bind is selected. In the Data Object Editor, from the menu, select Object > Bind.Alternatively, right-click the dimension object, and select Auto Bind.Warehouse Builder maps the attributes in the dimension to the database columns of the table that stores the dimension data. Note: When you create a dimension by using the wizard, OWB performs both the activities, creates the implementation table and then performs autobinding.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Manual Binding

Manual BindingIn manual binding, you must explicitly bind the attributes in the dimension to the database objects that store their data. You can either bind to existing tables or create new tables and bind to them. When to Use Manual BindingYou use manual binding when you want to bind a dimension object to existing tables or views. You use the Data Object Editor to perform manual binding. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Manual Binding

Manual Binding (continued)How to Perform Manual Binding

1. In the Data Object Editor, right-click the header area of the dimension, and select Detail view. Note that an additional tab appears on the Canvas header area next to the Business Definition tab.

2. Right-click the Canvas and select Add a Table or Add a View, depending on whether the dimensional data is stored in a table or view.

3. In the Add a New or Existing table dialog box, select an existing table or create a new table. Note that when you perform manual binding, in addition to mapping the attributes from the dimension object to the database object, you must also remember to map the level relationships. A level relationship is an association between levels in a dimension hierarchy.

When you create a hierarchy, OWB creates level relationships between the levels in the hierarchy. For example, the PRODUCTS dimension has the following hierarchy: TOTAL > CATEGORY > SUBCATEGORY > PRODUCT. OWB creates three level relationships: PRODUCT to SUBCATEGORY, SUBCATEGORY to CATEGORY, and CATEGORY to TOTAL.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Unbind

UnbindYou perform binding in the Data Object Editor. There are certain points to be noted when you perform autobinding:

• If the implementation method of the dimension object is same, OWB rebinds the dimension object to the existing implementation objects.

• If the implementation method of a dimension object is changed (for example, the implementation method has changed from Star to Snowflake), OWB deletes the old implementation and creates a new set of implementation tables. If you want to retain the old implementation’s objects, you must first unbind the dimension object, and then perform autobinding. Unbinding helps you to retain the old table only.

To unbind, right-click the dimension object, and select Unbind. Alternatively, from the Object menu, select Unbind.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Dimension Details: Data Viewer Tab

Dimension Details: Data Viewer TabThe Data Viewer tab is used to view the dimension data. You can view data by using the Data Viewer only after you have deployed and executed the dimension. In the lesson titled “Deploying, Loading, and Viewing Data,” you learn how to deploy the dimension and execute the mapping that loads the dimension objects.Using the Data Viewer, you can “see” the relational (ROLAP) and multidimensional data. It is hierarchically aware, enabling you to drill down into the data.So far, you have learned how to create a dimension by using the wizard. You have also learned how to use the Data Object Editor to edit a dimension. You also learned that, using the Data Object Editor, advanced users can create dimensions according to their requirement instead of using the default settings. Now you learn how to create the TIMES dimension by using the Time Wizard.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 7-2: Create a DimensionUsing the Editor

This practice covers creating the PRODUCTS dimension by using the editor.

Practice 7-2: Create a Dimension Using the Editor In this practice, you create one of the dimensions used in this course. You learn how to create a dimension by using the editor.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating the Time Dimension by Using the Time Wizard

Creating the Time Dimension by Using the Time Wizard Time dimensions are used extensively in data warehouses to address queries about time series, such as the following: What is the expense for this quarter as compared to the expense for the last year’s quarter? Note: Warehouse Builder enables you to not only create but also populate time dimensions. When you create a time dimension, Warehouse Builder automatically creates for you the mapping to populate the time dimension. Also, the data loaded into the time dimension conforms to the OLAP standards regarding attributes for a time dimension. You can use Warehouse Builder to create both fiscal and calendar time dimensions.Creating a Time Dimension Using the Time WizardTo create a time dimension by using the Time Wizard, perform the following steps:

1. In the Project Explorer, expand CLASS_PROJECT > Databases > Oracle > SALES_WH.

2. Right-click Dimensions, and select New > Using Time Wizard.The Create Time Dimension Wizard is launched.Editing a Time DimensionIf you have an existing data set, you can use the editor to create a completely customized time dimension. Just make sure to use the TIMESPAN and END DATE descriptors.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Time Dimension Wizard:Name and Description

Create Time Dimension Wizard: Name and DescriptionOn the Name and Description page, enter the following:

• A name for the dimension • A description (optional)

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Time Dimension Wizard: Storage

Create Time Dimension Wizard: StorageOn the Storage page, specify the type of storage for the dimension. The storage type determines how the dimension data is physically stored in the database.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Time Dimension Wizard:Data Generation

Create Time Dimension Wizard: Data GenerationOn the Data Generation page, you can specify additional information about the time dimension, such as the type of time dimension and the range of data stored in it. Range of data: You can specify the range of the temporal data stored in the time dimension. To specify the range, enter the following:

• Start year: The year from which to store data in the time dimension. You can enter the value or use the arrows to select the value.

• Number of years: The total number of years, beginning from the Start year, for which the time dimension stores data

Type of time dimension: You can specify the type of the time dimension to be created.• Calendar: Creates a calendar time dimension• Fiscal: Creates a fiscal time dimension

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Time Dimension Wizard: Levels

Create Time Dimension Wizard: LevelsOn the Levels page, you can select the calendar hierarchy that should be created and the levels that it should contain. You can select one from the two calendar hierarchy options:

• Normal HierarchyNormal Hierarchy contains the following levels:

- Calendar Year - Calendar Quarter - Calendar Month - Day

You must select the levels to be included in the calendar hierarchy. You must select at least two levels.

• Week HierarchyWeek Hierarchy contains two levels:

- Calendar Week - Day

Use Week Hierarchy to create a hierarchy that contains the Calendar Week level. When you select the Week Hierarchy option, both these levels are selected by default.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Time Dimension Wizard:Precreate Settings

Create Time Dimension Wizard: Precreate SettingsThe “Pre Create settings” page displays a summary of the options that you selected on the previous pages of the Create Time Dimension Wizard. This includes the following:

• Time dimension attributes • Time dimension levels • Time dimension hierarchies• Sequence• Name of the map that is used to populate the time dimension

Warehouse Builder uses these settings to create the objects that implement the time dimension.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Time Dimension Wizard:Progress Panel

Create Time Dimension Wizard: Progress PanelThe Time Dimension Progress Panel page displays the progress of the time dimension implementation. The progress status log section lists the activities that are performed by the Time Dimension Wizard to implement the time dimension.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Time Dimension Wizard: Summary

Create Time Dimension Wizard: SummaryThe Summary page summarizes the options selected on the wizard pages. Warehouse Builder creates the following objects:

• The time dimension object• The sequence that populates the surrogate ID of the time dimension levels • The physical structures that store the time dimension data

For a relational implementation, the database tables that store the dimension data are created in the repository. Warehouse Builder also binds the time dimension attributes to the database columns that store their values. A mapping that populates the time dimension is created for you by Warehouse Builder.Until now, you learned to create a dimension by using the wizard, and create or edit a dimension by using the Data Object Editor. You just learned how to create a time dimension by using the Time Wizard. OWB created the mapping that populates the time dimension. Now you learn how to create the other type of dimensional object, that is, cube. You create the cube by using the wizard.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 7-3: Create a TIMES Dimension Using the Time Wizard

This practice covers creating the TIMES dimension by using the Time Wizard.

Practice 7-3: Create a TIMES Dimension Using the Time WizardIn this practice, you create the TIMES dimension used in this course. You learn how to create the TIMES dimension by using the Create Time Wizard.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Defining a Cube Using the Wizard

SALES cubeDimensions

ProductsPromotionsChannels

CustomersTimes

MeasuresAmountQuantity

Cost

Sales_Products_FK

Sales_Channels_FKSales_Promotions_FK

Sales_Customers_FK

Customersdimension

Productsdimension

Timedimension

Promotionsdimension

Channelsdimension

Sales_Times_FK

Defining a Cube Using the WizardCubes contain measures and link to one or more dimensions. The axes of a cube contain dimension values and the body of the cube contains measure values. Most measures are numeric and additive. For example, sales data can be organized into a cube whose edges contain values for Time, Product, and Customer dimensions and whose body contains values from the Value Sales and Dollar Sales measures. In a relational implementation, a cube is linked to dimension tables by foreign key constraints and consists of a set of measures. To create a cube, you must define the following:

• Cube measures: A measure is a data, usually numeric and additive, that can be examined and analyzed. Examples of measures include sales, cost, and profit.

• Cube dimensionality: A cube must be defined by a set of dimensions. Note that a cube can refer to a level that is not the lowest level in a dimension.

Now you design a simple relational cube, SALES. To create a cube by using the wizard, perform the following steps:

1. In the Design Center, expand Databases > Oracle > SALES_WH.2. Right-click the Cubes node, and select New > Using Wizard.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Cube Wizard:Name and Description

Create Cube Wizard: Name and DescriptionOn the Name and Description page, enter the following details:Name: The name of the cubeDescription: A description for the cube (optional)

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Cube Wizard: Storage Type

Create Cube Wizard: Storage TypeOn the Storage Type page, specify the type of storage for the cube. The storage type determines how the cube is physically stored in the database. The following are the options for storage type:

• Relational storage (ROLAP): Warehouse Builder stores the cube definition and its data in a relational form in the database.

• Multi-dimensional storage (MOLAP): Warehouse Builder stores the cube definition and the cube data in an analytic workspace in the database. This is covered in the Oracle Warehouse builder 10g: Implementation Part 2 course.

Note: You select the storage type on the basis of the volume of the data stored at the lowest level of the entire cube and the refresh rate required. A cube is implemented using one fact table. The database object that is used to store the cube data is called a fact table.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Cube Wizard: Dimensions

Create Cube Wizard: DimensionsThe Create Cube – Step 3 of 4: Dimensions page defines the dimensionality of the cube. A cube is defined by a set of dimensions. The cube is linked to the dimension tables using foreign key constraints. Select all the dimensions that the cube refers to. For example, from the SALES_WH target module, select the five dimensions: CHANNELS, CUSTOMERS, PRODUCTS, PROMOTIONS, and TIMES.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Cube Wizard: Measures

Create Cube Wizard: MeasuresA measure is data, usually numeric, that can be examined and analyzed. Examples of measures include sales, cost, and profit. A cube must have one or more measures. The fact table contains columns for the measures and dimension references. On the Create Cube – Step 4 of 4: Measures page, define the measures of the cube. For example, enter the following three measures:Name Description Data Type Length Precision ScaleAMOUNT Sales Amount NUMBER 10 2

QUANTITY Sales Quantity NUMBER 0 0

COST Sales Cost NUMBER 10 2

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Cube Wizard: Summary

Create Cube Wizard: SummaryOn the Create Cube - Summary page, review the options that you specified in the previous steps of the Create Cube Wizard. Warehouse Builder creates the metadata for the following objects in the repository:For a relational implementation of a cube, you have the following:

• A table or view that stores the cube data• Foreign keys• For each measure, a column that stores the measure data• For each dimension reference, a column that stores the dimension reference

By default, OWB maps the cube to the lowest level in the dimension.Note: The wizard creates only the definition of all these objects. The actual objects are created when you generate and deploy the cube, and deploy and execute the cube mapping that loads the data into the cube. For more information, see the lesson titled “Deploying Loading, and Viewing Data.”

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Editing a Cube Using the DataObject Editor

Editing a Cube Using the Data Object EditorCreating the Cube Using the WizardYou just created a cube by using the wizard. Using the wizard to create a cube, you can create a cube quickly. Warehouse Builder uses default values for most of the parameters and creates the database structures that store the cube data.Creating or Editing the Cube Using the EditorYou use the Data Object Editor to create a cube when you want to specify certain advanced options, such as aggregation methods. Advanced users use the editor to create a cube to be able to use the options that are not available when you use the Create Cube Wizard.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Assigning Roles

Dimension roles in the Role drop-down list were created in the topic about dimensions. Here you assign the roles to the cube.

Assigning RolesYou learned how to create a dimension role on the Name tabbed page in the Dimension Details window of the Data Object Editor. Now, on the Dimensions tabbed page in the Cube Details window of the Data Object Editor, you assign the dimension role to a cube.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Configuring Cubes

Configure the physical properties of a cube.

Configuring CubesYou can configure the physical properties of a cube in one of two ways:

• From the Project Explorer, right-click the name of the cube you want to configure.• In the Data Object Editor, use the Configuration window.

You can configure the following cube properties:Deployable: If it is selected, the cube is deployed.Deployment Options: Use this to specify where the cube will be deployed:

• Deploy Aggregations: This deploys the aggregations defined on the cube measures.• Deploy All: For a relational implementation, the cube is deployed to the database and a

CWM definition to the OLAP catalog. For MOLAP implementation, the cube is deployed to the analytic workspace.

• Deploy Data Objects only: This deploys the cube only to the database. You can select this option only for cubes that have relational implementation.

• Deploy to Catalog only: This deploys the CWM definition to the OLAP catalog only. Use this option if you want applications such as Oracle Business Intelligence Beans or Discoverer for OLAP to access the dimension data after you deploy the data.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 7-4: Create a CubeUsing the Editor

This practice covers creating the SALES cube by using the wizard and modifying the cube by using the editor.

Practice 7-4: Creating a Cube Using the EditorIn this practice, you create the SALES cube used in this course. You learn how to create a cube by using the wizard and edit the cube by using the editor.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




SALES_WH

Mappings

Designing ETL Mappings

TIMES_MAP Mapping

LOAD_CHANNELS Mapping

LOAD_CUSTOMERS Mapping

LOAD_SALES Mapping

LOAD_PROMOTIONS Mapping

Created by the learner

Precreated for the learner

Created by OWB

LOAD_PRODUCTS Mapping

Designing ETL MappingsAfter designing the warehouse target and creating the dimension and the cubes, the next step is to design and build the extract, transform, and load (ETL) process. ETL involves the movement and transformation of data from your sources to your targets. In Warehouse Builder, you design the ETL process using mappings.You design mappings to load the PRODUCTS dimension and the SALES cube. To save time, the other three mappings are precreated for you. The mapping to load the time dimension was automatically created for you by OWB when you created the time dimension.You created a very simple mapping in the lesson titled “Defining Staging Metadata and Mapping Tables.”

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Mapping to Load the PRODUCTS Dimension

Mapping to Load the PRODUCTS DimensionThis mapping populates the PRODUCTS dimension by using a filter. Filter by IDThe CATEGORIES table contains data for both categories and subcategories. Categories have no value in the CATEGORY_ID column, and subcategories have a value in the CATEGORY_ID column. Filter Condition for the CATS Filter Operator INOUTGRP1.CATEGORY_ID is NULL.Filter Condition for the SUBCATS Filter Operator INOUTGRP1.CATEGORY_ID is not NULL.The rows are filtered and then put into the various levels of the PRODUCTS dimension.The TOTALS constant operator has two constant values: one for SOURCE_ID and the other for both Name and Description, which have the same values.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Mapping to Load the SALES Cube

Join condition: INGRP1.ID = INGRP2.ORDER_ID And

INGRP1.CUSTOMER_ID = INGRP3.CUSTOMER_ID And

INGRP1.PROMOTION_ID = INGRP4.ID

Mapping to Load the SALES CubeJoiner Brings Together Four TablesThis mapping uses a joiner operator to draw data from four relational tables: ORDERS, ORDER_ITEMS, ADDRESSES, and PROMOTIONS from the XSALES schema. The ORDER_ID, CUSTOMER_ID, PROMOTION_ID, CHANNEL, and ORDER_FINISHEDattributes from the ORDERS table pass information to the joiner operator. The metrics, such as COST, AMOUNT, and QUANTITY, from the ORDER_ITEMS table are passed on to the joiner. The ADDRESSES table passes to the joiner the customer details. The PROMOTIONStable passes the promotion details.The target is the SALES cube in the SALES_WH target warehouse. You add a key lookup operator to get CHANNELS_ID from the CHANNELS table on the basis of the channel’s Name. The TO_NUM_EXPR operator converts a date-type field to a number expression that is to be stored as a number in the cube.Join ConditionINGRP1.ID = INGRP2.ORDER_ID And INGRP1.CUSTOMER_ID = INGRP3.CUSTOMER_ID And INGRP1.PROMOTION_ID = INGRP4.ID

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y



Mapping to Load the SALES Cube (continued)AggregatorUsing a joiner operator, you join data from four source tables. The aggregator operator is used to aggregate the joined data with the data from another source table (CHANNELS). The aggregator performs data aggregations, such as SUM and AVG, and provides an output row set with aggregated data. Grouping is done on the following attributes: INGRP1.CITY_ID, INGRP1.PRODUCT_ID, INGRP1.ID, INGRP1.FINISH_MONTH, and INGRP1.SUBCATEGORY_IDThe output of the aggregator operator is then mapped to the target cube operator. The other mapping to load CUSTOMERS, PROMOTIONS, and CHANNELS will be created for you.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Pluggable Mapping

Pluggable MappingHere is an example of how OWB uses pluggable mapping. To see the example, perform the following steps:

1. Open the mapping editor for the LOAD_SALES mapping.2. Click the header area of the cube operator (SALES_OUT).3. On the toolbar, click Expand Child Graph.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Generating the Mappings

Generating the MappingsYou have designed the dimensional model, dimensions, and cube. You then designed the ETL mapping. Now you generate the code for the mapping. Two Ways of Generating Code for a MappingIn the Project Explorer, right-click the mapping, and select Generate. The Generation Results window displays the results. Alternatively, perform the following steps:

1. Double-click the respective mapping. The Mapping Editor is launched.2. In the Mapping Editor, from the menu, select Mapping > Generate.

On the basis of the ETL logic that you designed in the mapping, Warehouse Builder generates the code required to implement your design.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Summary

In this lesson, you should have learned how to:• Define dimensions and cubes • Navigate the Data Object Editor• Define ETL mappings to load the dimensions

and cubes

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 7-5: Design ETL Mappings

This practice covers creating the LOAD_PRODUCTSmapping.

Practice 7-5: Design ETL Mappings So far in this lesson, you created:

• The PRODUCTS dimension by using the Dimension Editor• The TIMES dimension by using the Time Wizard

After designing the dimensions, you created the SALES cube by using the wizard and modified it using the editor.After designing the dimensional objects, you now learn how to create ETL mappings to load dimension objects.In this course, you learn how to design the LOAD_PRODUCTS mapping, a mapping to load the PRODUCTS dimension. To save time during this course, the LOAD_SALES mapping, the mapping to load the SALES cube, is created for you. If you want to create it yourself, follow the guided steps in the appendix titled “Create the LOAD_SALES Mapping” of this course.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y



Handling Slowly Changing Dimensions

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Objectives

After completing this lesson, you should be able to do the following:• Explain how Oracle Warehouse Builder (OWB)

handles a slowly changing dimension• Define a type 2 slowly changing dimension• Use the type 2 policy dialog box

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




What Is a Slowly Changing Dimension?

A slowly changing dimension (SCD) is a dimension that stores and manages both current and historical data over time in a data warehouse.

What Is a Slowly Changing Dimension?A slowly changing dimension (SCD) is a dimension that stores and manages both current and historical data over time in a data warehouse. It is considered and implemented as one of the most critical extract, transform, and load (ETL) tasks in tracking the history of dimension records.Note: You can create SCDs only for dimensions that use a relational implementation.Examples of Slowly Changing DimensionsA product package size, package type, or price may change over time. People change their names for some reason. Names of countries and states may change over time. Some changes happen to a dimension over a period of time. A dimension that changes over time is called a slowly changing dimension.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Types of Slowly Changing Dimensions

There are three types of slowly changing dimensions:• Type 1 overwrites old values.• Type 2 creates another dimension record.• Type 3 creates a current value field.

Types of Slowly Changing DimensionsThere are three types of SCDs:Type 1 overwrites old values: Type 1 is the default SCD. It does not store history. Only one version of the dimension record exists.Type 2 creates another dimension record: Type 2 preserves history. A new record is created.Type 3 creates a current value field: Type 3 also preserves history. For a type 3 SCD, two versions of values for a selected level attribute are stored. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Type 1 SCD: Does Not Store History

Type 1 overwrites old values.

ID Customer ID Marital Status1125 Single

Customer Name3 Steve

ID Customer ID Marital Status1125

Customer Name3 Steve Married

Old record

New record

Type 1 SCD: Does Not Store HistoryType 1 is the default selection. In a type 1 SCD, the new data overwrites the existing data. Oracle Warehouse Builder (also called as Warehouse Builder or OWB) creates a dimension that does not store history. This is a normal dimension. You do not need to specify any additional information to create a type 1 SCD.For example: ID Customer ID Customer Name Marital Status3 1125 Steve SingleIf Steve’s marital status changes, the new data overwrites the existing data, and the new record looks like the following:ID Customer ID Customer Name Marital Status3 1125 Steve MarriedThis is the easiest way to handle an SCD. There is no need to store the old information. However, there is no way to keep track of the old information. It is not possible to trace Steve’s previous marital status.You use a type 1 SCD when it is not necessary for the data warehouse to keep track of historical changes.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Type 2 SCD: Preserves Complete History

Type 2 stores complete change history.

Closed recordOpen/Current record

1125 Single3 Steve 04-04-1999 01-13-20011125 Married8 Steve 01-14-2001 NULL

1125 Single3 Steve 04-04-1999 NULL

Before

After Open/Current record

ID Customer

ID

Marital

Status

Customer

Name

Effective

Date

Expiration

Date

ID Customer

ID

Marital

Status

Customer

Name

Effective

Date

Expiration

Date

Type 2 SCD: Preserves Complete HistoryIf you are creating a new dimension using the wizard, Warehouse Builder creates the following two additional dimension attributes: effective_time and expiration_time. And, it makes these two attributes applicable for the lowest level. All the attributes of the lowest level in the type 2 SCD, except the surrogate and business identifier, are defined as the triggering attributes.Note: If you use the Data Object Editor, you must add the two attributes on the Attributes tabbed page. On the Levels tabbed page, apply the two attributes to the lowest level. Using the same example used on the previous page, when the marital status for Steve changes from Single to Married, the old record is closed and a new record is added to the table. The new record gets a new value for ID.ID Customer ID Customer Name Marital Status Effective_Date Expiration_Date3 1125 Steve Single 04-04-1999 01-13-20018 1125 Steve Married 01-14-2001You use the type 2 SCD when it is necessary for the data warehouse to track historical changes.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Type 3 SCD: Stores Onlythe Previous Value

1125 Married3 Steve Single 01-14-2001

ID Customer

ID

Marital

Status

Customer

Name

Previous Marital Status

Effective

Date

1125 Widower3 Steve Married 10-30-2004

Type 3 SCD: Stores Only the Previous ValueA type 3 SCD stores two versions of values for certain selected level attributes. Each record stores the previous value and the current value of the selected attribute. When the value of any attribute changes, the current value is stored as the old value and the new value becomes the current value. In a type 3 SCD, a new attribute is created for the old marital status. Using the same example, if Steve’s marital status changes from single to married, the record would look like this:ID Customer ID Customer Name Marital Status Prev_Marital Status Effective Date3 1125 Steve Married Single 01-14-2001If Steve’s marital status changes from married to widower, the record would look like this:ID Customer ID Customer Name Marital Status Prev_Marital Status Effective Date7 1125 Steve Widower Married 10-30-2004The only concern with the type 3 approach is that if the marital status changes over the years, then the complete history may not be stored; only the latest change will be stored. For example, if the marital status changes in the year 2005, then you would not be able to see the complete history.Note: Neither the surrogate ID nor the business key can have previous values. (Any key cannot have the previous value.)

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating a Type 2 SCD Usingthe Dimension Editor

When creating a type 2 SCD by using the editor: • The attributes that store the effective time and

expiration time are:– EFFECTIVE_DATE

– EXPIRATION_DATE

• Identify the attribute that triggers history saving

Creating a Type 2 SCD Using the Dimension EditorIn this example, you create a type 2 SCD by using the Dimension Editor. To create a type 2 SCD by using the dimension editor, note the following:

• The attributes that store the effective time and expiration time• The attribute that triggers history saving

In the Data Object Editor, on the Attributes tabbed page, add these two attributes:Name Data TypeEFFECTIVE_DATE DATE

EXPIRATION_DATE DATEO

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Creating a Type 2 SCD

Creating a Type 2 SCDIn the Data Object Editor, on the Levels tabbed page, apply the two attributes to the lowest level.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y





Creating a Type 2 SCD (continued)In the Data Object Editor, on the SCD tabbed page, select “Type 2: Store the complete change history,” and click Settings.The “Type two slowly changing policy” window appears.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y





Creating a Type 2 SCD (continued)In the “Type two slowly changing policy” window, you can specify the effective date attribute, expiration date attribute, and the versioned attribute. The dialog box displays four columns: Levels, Identifying Attribute, Data Type, and Record History. Identify the level that has the two additional attributes that store the effective time and expiration time. Perform the following steps:

1. Select the attribute that triggers history saving. In the Record History column, select “Trigger history” from the drop-down list.

2. Select the EFFECTIVE_DATE row. In the Record History column, select “Effective date” from the drop-down list.

3. Select the EXPIRATION_DATE row. In the Record History column, select “Expiration date” from the drop-down list.

In this example, when the value of Name in the Channel level changes, the existing record is closed and a new record is created using the latest values.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y





Creating a Type 2 SCD (continued)Dimension EditorAfter you have completed creating a type 2 SCD, in the Dimension Editor, right-click the dimension and select Auto Bind.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Mapping to Load the Type 2 SCD

Mapping to Load the Type 2 SCDIn the Mapping Editor, right-click the dimension, and select Synchronize. You now see that the two attributes that you added appear on the level that you selected.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating a Type 2 SCD Using the Wizard

Creating a Type 2 SCD Using the WizardWhen you can create a type 2 SCD by using the Dimension Wizard, use the wizard’s Data Policy page to select “Type 2: Store the complete change history.” Warehouse Builder creates the two attributes: EFFECTIVE_TIME and EXPIRATION_TIME. It also applies the two attributes to the lowest level. On the “Type two slowly changing policy” page, at the lowest level, all attributes other than the Surrogate and Business key attributes are selected as trigger history attributes. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Dimension Operator in a Mapping

Date control mechanisms for the type 2 SCD

Load control mechanisms

Regular dimension

Orphan management mechanisms

Dimension Operator in a MappingDimension Operator PropertiesThe dimension operator properties are used to set options that define the method in which data is loaded into the dimension. Loading Type: There are two choices: LOAD and REMOVE. LOAD updates the existing data and loads the new data. REMOVE deletes the existing data.Default Effective Time of Open Record: The value specified here becomes the default value for the effective time of the current record for SCDs.Default Expiration Time of Open Record: The value specified here is the expiration time of a newly created open record.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Group Properties in the Dimension

Specify the condition to indicate whether it is an open record or a closed record.

Condition used if dimension is a source

Group Properties in the DimensionGroup PropertiesThe groups in the Dimension operator that represent the dimension levels have additional properties.Close Record Condition: Specify an expression that serves as the condition clause to indicate whether it is a closed record.Open Record Condition: Specify an expression that serves as the condition clause to indicate whether it is an open record.Extracting Type: If the dimension is used as a source, use Extract Current Only (Type 2 Only) to specify that only the current records be extracted.Note: The settings of the group parameters presented here are just for your information. If you use the default options, you do not need to set these parameters with values.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y





Creating a Type 3 SCDOn the Create Dimension – Step 6 of 8: Data Policy page, select “Type 3: Store only the previous value.” Warehouse Builder creates an attribute to store the previous value of each trigger attribute. Also, an additional attribute EFFECTIVE_DATE is created. In a type 3 SCD, the current values of the changed attributes are moved to the attributes that store the previous values and the new values are stored in the attributes.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Attributes in a Type 3 SCD

Attributes in a Type 3 SCDExamine the following example:ID Customer ID Customer Name Marital Status Prev_Marital Status Effective Date3 1125 Steve Married Single 01-14-2001If Steve’s marital status changes from Married to Widow, the record would look like this:ID Customer ID Customer Name Marital Status Prev Marital Status Effective Date7 1125 Steve Widower Married 10-30-2004

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Summary

In this lesson, you should have learned how to:• Define a type 2 slowly changing dimension• Use the type 2 policy dialog box

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 8-1: Handling Slowly Changing Dimension

This practice covers creating a type 2 slowly changing dimension.

Practice 8-1: Handling Slowly Changing DimensionCreating a Dimension Using the WizardIn this practice, change the existing channel’s dimension from the default type 1 dimension to a type 2 dimension.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y



Using Process Flows

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Objectives

After completing this lesson, you should be able to do the following:• Navigate the process flow editor• Create process flow definitions• Define a schedule• Use the process flow enhancements:

– Activity templates– New activities:

– Loop – Notifications– Wait

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Course Progress Report1. Define the source metadata.








9. View the data.

Course Progress ReportIn Oracle Warehouse Builder (also called as Warehouse Builder or OWB), extract, transform, and load (ETL) consists of two main areas:

• Mappings (or data flow diagrams)• Processes (or process flow diagrams, which can contain multiple mappings)

In this lesson, you learn how to define and create process flows.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Process Flow Concepts

PROCESS_FLOW_MODULE

Process_Flow_Package1

Process flow 1

Process flow 2

Process flow 3

Process flow module

Process flow package

Process flow

Process_Flow_Package2

Process Flow ConceptsProcess flow module: A process flow module contains all process flows. A process flowmodule can be compared to a target module that contains all target objects.Process flow package: A process flow package is the smallest unit of deployment and is synonymous with a PL/SQL package. The process flow package is a grouping mechanism that determines which process flows you can interrelate. A process flow from one process flow package can launch a process flow from another process flow package. Process flow: A process flow is a chain of mappings and other external activities in a single processing entity, in which you know the dependencies and the sequence of activities as well as the error handling of the process.Activity: An activity is a single unit of work for the process—for example, a mapping or the FTP activity.Status: This returns the status of an activity, which can be Success, Warning, or Error.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating a Process Flow Module

Creating a Process Flow ModuleBefore you create a process flow, create a process flow module. The process flow module contains process flow packages, which include process flows.To create a process flow module, perform the following steps:

1. In the Project Explorer, expand the CLASS_PROJECT project. Expand Process Flows.2. Right-click Process Flows Modules, and select New. The Create Module Wizard is

launched.3. On the Name and Description page of the wizard, enter a module name and, optionally,

a description. Click Next.4. On the Connection Information page, enter the connection details.

Note: Install the Oracle Workflow server as part of Oracle Database 10g Release 2. (By default, Oracle Workflow is not selected as a component to be installed.) For this course, the workflow server is installed in a workflow server schema owf_mgr (default username is OWF_MGR). The OWF_MGR_LOCATION location points to a workflow engine OWF_MGRthat runs in the target database.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating a Process Flow Package

Creating a Process Flow PackageAfter creating the process flow module, the Create Module Wizard automatically launches the Create Process Flow Package Wizard. In the Create Package Flow dialog box, enter a name and description for the process flow package.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating a Process Flow

Creating a Process FlowAfter creating the process module and the process flow package for process flows, you can create the process flow.The Create Module Wizard displays the Create Process Flow page. Specify a name and description for the process flow. Warehouse Builder launches the process flow editor and displays the process flow with a START1 activity and an END_SUCCESS activity. A process flow ensures that a set of mappings is executed in the correct order and handles exceptions and notifications in an automated way. The things you conceptually do to create a process flow are:

• Determine the dependency and sequence of activities.• Determine what to do for every status for each activity.• Set the statuses and ensure that the process flow does not get into an endless loop.• Model atomic activities and activities (such as FTP and FILECHECK) in the process

(not in the mapping).• Model explicit Success, Error, and, if need be, Warning END activities.• Validate the process flow.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Process Flow Editor

Bird’s EyeView

ObjectDetails

Palette

Explorer

Process Flow EditorThe look-and-feel of the process flow editor in Warehouse Builder is also in line with the look-and-feel of all the other editors. Explorer: This panel has two tabs:

• Available Objects: Use the selection tree to drag objects from the OWB repository directly into the process flow.

• Selected Objects: An object tree contains all objects in the process flow. Use this panel to set properties of definitions or remove definitions. Variables can also be defined from here using the Create button.

Object Details: Use this to set attribute values for individual properties. Most attributes enable you to specify a value or a binding. The binding binds the value to the value of a variable in the context of the process flow.Main Canvas: The graphical options (zoom, autolayout, and so on) are used in this canvas to create the process flow.Palette: Use the palette to bring in individual activities not bound to other objects in the repository. You can create new mappings in the process flow using Synchronize (outbound reconcile). Reconciliation in the context of process flows is also available.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Types of Activities

Types of ActivitiesIn a process flow, the basic elements include activities and transitions. An activity is a single unit of work for the process flow, such as launching a mapping or verifying the existence of a file. When you design a process flow in Warehouse Builder, you select activities from the palette. Warehouse Builder includes different types of activities:OWB-Specific ActivitiesThese activities enable you to launch Warehouse Builder activities such as mappings, transformations, and other process flows.Utility ActivitiesThese activities enable you to perform services such as sending e-mails.Control ActivitiesThese activities enable you to control the progress and direction of the process flow. For example, the Fork activity launches multiple activities concurrently.Note: You can reuse the parameters of the Utility and Control activities by creating an activity template. An activity template enables you to define a template for an activity that you can reuse in your process flows.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Adding a Fork Activity

Launches two or more activities after completing an activity

Adding a Fork ActivityYou use the fork activity to launch multiple concurrent activities after the completion of an activity.To add a fork activity to the LOAD_SALES_WH process flow, perform the following tasks:

1. From the Palette panel, select Control Activities from the drop-down list.2. Drag the Fork activity to the canvas.

To move the activities within the canvas, perform either of the following steps:• Point the mouse pointer to the activity name below the activity. The mouse pointer

changes to a single head arrow. Now click and drag the activity to anywhere on the canvas.

• Select the activity. Click the header area of the activity and keep the left mouse button clicked, and move the activity to anywhere on the canvas.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Adding a Mapping Activity

Adding a Mapping ActivityYou can add an existing mapping activity to the process flow by performing these steps:

1. In the Process Editor, click the Available Objects tab in the Explorer panel.2. Expand the SALES_WH target module. Select all the desired mappings and drag them

onto the canvas.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Adding an And Activity

Adding an And ActivityYou use the And activity to specify the completion of two or more activities before resuming the process flow. Note: The correct usage of an And activity in the process flow is that you must place a Fork activity upstream of the And activity. Also, the number of transitions going into the And activity must be less than or equal to the number of transitions going out of the upstream Fork activity. Only the And and Or activities can have multiple incoming transitions. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Adding End Activities

Adding End ActivitiesThe end activity types are used for error-handling logic. An end activity can have three possible results. The following are some end activities:EndBy default, the END_SUCCESS activity is created for every process flow. The success activity indicates that the path contains logic that is dependent on the successful completion of an upstream activity. End with ErrorsAssign a path as ending with errors.End with WarningsAssign a path as ending with warnings.Note: You can have only one of each ending type.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating Transitions Between Activities

Adding Transitions Between Activities Transitions indicate the sequence and conditions in which activities occur in the process flow. You can use transitions to execute an activity based on the completion state of the preceding activity. To add a transition, perform the following steps:

1. Place the cursor in the center of the source activity until you see the single head arrow, indicating that you can now connect the activities.

2. With the left mouse button clicked, move towards the activity that you want to connect. As you begin to scroll from the source to the target, you see the cursor changes to have a plus sign below its single-head arrow. When you reach an activity, the plus sign changes to a circle. If you release the left mouse button, the two activities are connected.

Warehouse Builder assigns a default transition name. The arrow between the two activities is called a transition.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Transition Conditions

Transition ConditionsYou just learned how to draw transitions. These transitions are unconditional by default. You can apply conditions to the transition. To apply a condition to the transition, perform the following tasks:

1. Select the transition to which you want to add a condition.2. In the Object Details window, select CONDITION. On the right, click “:” (the colon

button). The Transition Condition Editor is launched.You use the Transition Condition Editor to specify the enumerated conditions or write an expression for a complex condition. Enumerated ConditionsSuccess: The process flow continues only if the preceding activity ends in success.Warning: The process flow continues only if the preceding activity ends with warnings.Error: The process flow continues only if the preceding activity ends in an error.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Generating the Process Flow

Generating the Process FlowEnsure that you have a workflow location and you have associated that location with the process flow module. Validating the Process FlowValidate all objects to ensure that no definitions are invalid or incomplete. In the Process Editor, select Validate from the Process Flow menu.Generating the Process FlowIn addition to validating object definitions before deployment, you can also generate and view the scripts. During this process, Warehouse Builder validates the object definitions and generates the scripts required to create and populate the objects. You can then view the generation results and the code generated for each script. When you generate the code, you can also save it if you want to deploy it from outside Warehouse Builder.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 9-1: Create the LOAD_SALES_WHProcess Flow

This practice covers creating the LOAD_SALES_WHprocess flow.

Practice 9-1: Create the LOAD_SALES_WH Process FlowIn this practice, you define the LOAD_SALES_WH process flow. You chain together the mappings and the related processes. The dimensions (LOAD_CHANNELS, LOAD_PRODUCTS, LOAD_PROMOTIONS, LOAD_CUSTOMERS, and TIMES_MAP) must be loaded before the cube (LOAD_SALES) because the cube references the dimension values. Only after all the dimensions are successfully loaded will the loading of the cube start. You use the end activity in a path in a process flow to indicate the type of logic contained in a path. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




New Concepts in Process Management

Activity templates- Specify settings

on activity once.- Use them multiple times.

Variables- Pass information

between activities.- Store output of a mapping,

save it as a variable, anduse it later.

New activities- Loop- Notification- Wait- SQL*Plus scriptand much more

New outcomes

-Your own outcomes

In addition to:- Success- Warning- Error

New Concepts in Process ManagementOracle Warehouse Builder 10g Release 2 introduces new concepts in process management in general, and the process flow editor in particular.Activity TemplatesActivity templates enable you to define a template for an activity that you can reuse in your process flows. You would set a number of settings on an activity once and use them multiple times in your process flows. Also, if any of the settings in the template change, then Warehouse Builder knows where the template was used so that you can propagate these changes.VariablesVariables and the variable store enable you to pass information between activities. You can have output parameters in one activity, store the value in a variable, and reuse the value further downstream in another activity.New ActivitiesThere are many new activities, including loop, notification, wait, and SQL*Plus script.More Activity OutcomesSome activities enable more outcomes than just SUCCESS, WARNING, and ERROR. You can enumerate your own outcomes and use those in order to direct the dependency flow.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating Activity Templates

Creating Activity TemplatesActivity templates enable you to define a template for an activity that you can reuse in your process flows.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating Activity Templates

Example:Set these default e-mail parameters once.Reuse in all e-mail activities!

Creating Activity Templates (continued)Typical E-Mail Activity TemplateOn the basis of your organization’s management requirements, you know that you need to set up an e-mail activity to be used on a very frequent basis. In earlier releases of Warehouse Builder, you had to set the properties for the e-mail activities (such as “SMTP server,” “from address,” and “to address”) individually for eachactivity. Now you can create a template that has these values preset. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Process Flow Activities

• For Loop• Route Activity• While Loop

• Assign Activity• Manual Activity• Notification• Set Status• Sqlplus

Activity• Wait Activity

Process Flow ActivitiesWarehouse Builder exposes a number of new process flow activities. These are the building blocks for more complex process flows. Some of these new activities are discussed on the following pages.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating a Variable

Variables are defined using the Explorer panel.

Creating a VariableIn the Explorer panel, select the Variables node, and click the Create button.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Assign Activity

The Assign activity enables you to assign a value to a variable in the context of a process flow.

Assign ActivityYou use this activity to assign a value to a variable.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Data Auditor

• The data auditor enables you to include a data profiling activity in the context of a process flow.

• For example, you may want to direct your process flow depending on the quality of the data you receive.

Data Auditor The data auditor folder resides within an Oracle database tree. The data auditor is designed to quantify the quality of the data in tables, views, materialized views, and external tables through processing data rules.The data auditor has the following parameters:• PURGE_GROUP implements the purge group.• AUDIT_LEVEL is the audit level.• THRESHOLD_TYPE is the type of threshold: Defects, Process Sigma, or None.• DEFECTS_THRESHOLD enables you to specify the number of errors you want to

allow for the data analysis.• SIX_SIGMA_THRESHOLD enables you to specify the six-sigma threshold value.• AUDIT_RESULT returns the result of the audit: PASSED (no thresholds exceeded and

no anomalies), PASSED WITH WARNINGS (no thresholds exceeded, but some anomalies identified), or NOT PASSED (threshold exceeded).

• RETURNS returns the execution status: SUCCESS, WARNING, or ERROR.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




For Loop Activity

• FOR_LOOP enablescreating loops.

• FOR_LOOPenables you to define aconstruct that repeats.

• Before every entryinto the loop, a variablevalue is updated.

Createvariable.

FOR_LOOPcondition usesvariable.

For Loop ActivityFOR_LOOP has the following parameters:• CONDITION: The condition that is evaluated to identify whether the loop must

continue• INITIAL_VALUE: The initial variable value on entering the loop• NEXT_VALUE: The increment value for the variable • VARIABLE: The reference to the variable that is used in the loop. You can read the

variable value in other activities in the loop.Transitions that flow out of FOR_LOOP have to be given a condition: loop or exit. These values are enumerated on the conditions out of the operator. All flows out of the loop have to converge at an END_LOOP activity. A diagrammatic representation of FOR_LOOP:

exitSTART ---------------->FOR_LOOP---------------------> END_SUCCESS

^ || |

END_LOOP | loop^ || || v

TEST_PROCEDURE

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Route and While Loop Activities

• ROUTE is just a node with no operation and so can beused as an elbow for a line.

• WHILE_LOOP implements the functionality of a WHILEstatement that is available in most programming languages.

• Before entering the loop, the WHILE_LOOP activity is evaluated to see whether the condition still allows the loop.

If variable < X,go this way;else go that way.

While conditionis true,perform a task.

Route and While Loop ActivitiesRoute ActivityThe ROUTE activity enables you to route the outcome of an activity to specific results on the basis of a user-defined condition.While Loop ActivityThe transitions flowing out of WHILE_LOOP have to be set either to loop or to exit(compare with FOR_LOOP). All lines that flow out of WHILE_LOOP have to converge in the END_LOOP activity. WHILE_LOOP has the same semantics as FOR_LOOP, but you cannot set variables.WHILE_LOOP contains only one parameter, CONDITION, which specifies whether or not to continue the loop.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Manual Activity

• The manual activity indicates that the process flow would be halted until a manual response is performed by a person.

• The user can respond to the manual activity in the Control Center browser, and define the result (SUCCESS, WARNING, or ERROR).

• The process flow continues accordingly.

Manual ActivityThe manual activity has the following parameters:• PERFORMER: The name of the person, or group or role that has to execute the activity• PRIORITY: LOW, NORMAL, or HIGH• SUBJECT: The subject of the activity• TEXT_BODY: The content of the activity. Notice that even though the parameters of

the manual activity are similar to the parameters of the notification, the manual activity does not send out an e-mail. Typically, you would notify the person or group that an activity needs to happen.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Notification Activity

• The notification activity enables integration with Oracle Workflow’s notification mechanism.

• Notifications enable a framework in which users can be sent messages (in the form of e-mails) to which they have to respond.

• The responses define the outcome of the notification.

• The process flow can be directed based on these responses.

For restartability or recoverability, this is a very important feature!

Notification ActivityFor example, if a mapping fails, you can send a notification to an administrator to fix the issue. The process flow waits for a response from the administrator, which, for example, can be Continue or Stop. Perhaps the administrator fixes the data issue, reruns the mapping that failed, and then decides to continue the process flow. For restartability or recoverability, this is a very important feature. Note: When you create a process flow notification, an Oracle Workflow notification is deployed for you; there is no additional effort required by the user.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Set Status Activity

• The SET_STATUS activity enables you to set the status of the outcome to SUCCESS, WARNING, or ERROR.

• After the activity, the result is whatever you specify in the SET_STATUS activity.

Set Status ActivityThe SET_STATUS activity enables you to force or overrule the status of the outcome to SUCCESS, WARNING, or ERROR—that is, after the activity, the result is whatever you specify in the SET_STATUS activity. This is particularly useful when used in conjunction with the AND or OR activities to assign a status to an incoming transition path that normally has one—for example, an outgoing transition from the Fork activity can be given a status through SET_STATUS. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




SQLPLUS Activity

With the SQLPLUS activity, you can run any (parameterized) SQL*Plus script in the process flow editor.

SQLPLUS ActivityThe script can be stored in the file system and referenced in the parameter list.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Wait Activity

• The WAIT activity enables you to specify a wait.

• For example, in the context of a loop, you may want to wait five minutes while polling if a file exists.

Wait ActivityThe WAIT activity has two parameters:• MINIMUM_DELAY: The minimum time it will wait (This value is specified in

seconds.)• UNTIL_DATE: Date until which the activity will wait

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Scheduling Concepts

Schedule_Module 1

EVERY_2_HOURS

MONTHLY_SALES

SALES_EVERY_30_MIN

Schedule_Module 2

HOURLY_LOAD

Scheduling ConceptsIn the Project Explorer, you see the Schedules node. The Schedules node contains schedule modules and schedules within the module. Schedule module: Schedule modules are containers for different schedules. A schedule module can be compared to a process flow module or a target module in OWB. You create the schedule module by using the Create Module Wizard.Schedule: You use schedules to plan when and how often to execute operations that you deploy through Warehouse Builder (for example, mappings and process flow).

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating a Schedule Module

Creating a Schedule ModuleBefore creating a schedule, you create a schedule module. Creating a schedule module is necessary for creating a schedule in a new project. To create a schedule module, perform the following steps:

1. In the Project Explorer, expand CLASS_PROJECT.2. Right-click the Schedules node, and select New. The Create Module Wizard is

launched. Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating a Schedule

Creating a ScheduleHow Schedules Are DefinedSchedules are defined by:Start date and time: When does the schedule first wake up?Schedule frequency: How often does the schedule wake up?Repeat interval: How frequently does the schedule execute when active?End date and time: When is the schedule deactivated again?In this topic, you learn how to create a simple schedule that is meant to run every two hours.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Schedule Wizard:Name and Description

Create Schedule Wizard: Name and DescriptionOn the Name and Description page, perform the following tasks:

1. Enter a name for the schedule.2. Enter a description (optional).

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Schedule Wizard:Start and End Time

Create Schedule Wizard: Start and End TimeThe start and end dates and times define the duration for which the schedule is valid. Specify the start and end dates and times.

• Specify the time zone. Use the drop-down list.• You can accept the default start date or specify a time in the future. • Change the default end date, which is the same as the default start date.

Note: To change from a.m. to p.m. or change hours, minutes, or seconds, highlight and use the arrow keys.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Create Schedule Wizard:Frequency and Repeat Interval

Create Schedule Wizard: Frequency and Repeat IntervalFrequencyUsing the frequency unit, specify how often you want the schedule to “wake up.” The possible values are Yearly, Monthly, Weekly, Daily, Hourly, Minutely, and Secondly. RepeatThe values available for the Repeat Every field vary, depending on the value you supply in the Frequency field.Note: The wizard does not provide all the available scheduling capabilities. After you finish creating a schedule by using the wizard, you can access the schedule’s editor to specify more advanced scheduling capabilities.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Monthly Schedule

Monthlyfrequency

Repeatinterval

Day ofmonth

Monthly ScheduleIn this screenshot, a schedule is specified to run once a month, starting on the first day of each month.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Editing a Schedule

Specificationsfrom the wizard

Additionaladvancedspecificationsin the editor

Schedule willrun at 9 a.m., 11 a.m., 1 p.m., 3 p.m., and 5 p.m.

Schedulepreview

Editing the ScheduleAfter you have created the schedule with the wizard, you can provide more advanced specifications by using the schedule’s editor. The Create Schedule Wizard does not give you all the capabilities to edit the schedule. Now you learn how to edit the schedule that you created.In this screenshot, the hours of 9, 11, 13, 15, and 17 have been specified. Because the start time is specified as 00:00:00AM Pacific Standard Time, the effective times are 9 a.m., 11 a.m., 1 p.m., 3 p.m., and 5 p.m.Previewing the ScheduleYou can preview the schedule execution times you have specified. The preview refreshes instantly when you change anything in the schedule.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Schedule Example

Runquarterly.

Run on the8th day aftereach quarter.

Schedule ExampleRun One Week into the Next QuarterIn this example, the specification is for the schedule to run one week after the beginning of each quarter. The start date, which would be the first day of the first quarter, is not shown.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Associating Executable with a Schedule

Associateexecutablewith a schedule.

Databasescheduler

Deploy

Schedule

- Start date and time

- Schedule frequency

- Repeat interval

- End date and time

Executable object

- Mapping

- Transformation

- Process flow

Associating Executable with a ScheduleYou can define your own schedules in Warehouse Builder and associate your executable objects within the schedules. An executable object (for example, mapping and process flow) can be associated with a schedule. On the deployment of Warehouse Builder, Warehouse Builder deploys the schedule into the database scheduler.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Assigning a Scheduleto an Executable Object

A scheduleassigned to theLOAD_SALESmapping

The LOAD_SALES mapping configuration properties:

Assigning a Schedule to an Executable ObjectYou associate a schedule with an executable object in the configuration of the executable object. In this example, the LOAD_SALES mapping is configured to be assigned to the ONE_WK_INTO_EACH_QTR schedule.Make sure to set the execution location to an Oracle database location in order for the deployment to pick up the schedule. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Summary

In this lesson, you should have learned how to:• Navigate the process flow editor• Create process flow definitions• Define a schedule• Use the process flow enhancements:

– Activity templates– New activities:

– Loop – Notifications– Wait

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 9-2: Create a Schedule

This practice covers the following topics:• Defining schedules• Defining activity templates• Defining notifications

Practice 9-2: Create a ScheduleIn this practice, you learn how to define your own schedules. For example, during the day, operations managers have to see how sales are happening so that products that are about to expire can still be discounted during the day. The refresh frequency is two hours. You learn how to create an activity template that you need to set up an e-mail activity to be used on a very frequent basis.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y



Deploying, Loading, and Viewing Data

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Objectives

After completing this lesson, you should be able to do the following:• Use the Control Center Manager• Load data into tables• Use the Dependency Manager to manage metadata

ObjectivesUntil now you have designed and configured the logical definitions of your target system. Now you learn how to deploy and create the physical instance of your target.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y













9. View the data.

Course Progress ReportIn this lesson, you learn how to use the Control Center Manager to deploy objects and execute mappings. Finally, you view the result of your work by viewing the data by using the Data Viewer.Scenario

• The source module used in this course is XSALES and has been precreated for you.• The target module used in this course is SALES_WH and has been precreated for you.• In the lesson titled “Defining a Relational Dimensional Model,” you created two

dimensions (CHANNELS and PRODUCTS) and one cube (SALES). • In the lesson titled “Using Process Flows,” you defined a process flow

(LOAD_SALES_WH), which, when deployed and executed, loads data into all the five dimensions and the cube. You use the Data Viewer to view the data in the dimensions and the cube.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Logical Versus Physical

Logical model(Created metadata at a logical-design level)

Physical implementation(Creates physical database structures)

Logical Versus PhysicalUntil now you have designed and configured the logical definitions of your target system. You are now ready to deploy and create the physical instance of your target. After you have created the metadata at a logical-design level, you work at the physical level, using Oracle Warehouse Builder (called as Warehouse Builder or OWB) to generate and execute code that creates physical database structures.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Physical Implementation

Build and populate warehouse tables.

Validate (optional).

Configure for physicalimplementation.

Generate build andextraction scripts.

Deploy warehouse scripts.

Fix errors.

OWBControl Center

Manager

Oracle8i/9i/10g R1/10g R2

To database

To files

For laterdeployment

Physical ImplementationConfigure for physical implementation: Specify configuration settings, such as partitioning and sequence start values.Validate the configuration: This step is optional because it is performed automatically before generating scripts. The validation tool tests whether your logical objects are ready for physical implementation. These are validation tests for issues such as data-type mismatches, missing keys, and naming-convention errors. Fix errors: The validation test results indicate errors that must be fixed. Generate scripts: The Generate facility creates scripts for building physical warehouse objects and scripts for extracting data to them. The scripts generated are for viewing and verification purpose only and may not be deployable.Deploy scripts: You can deploy the scripts either directly to a target database (as in this class) or to the host file system for later deployment.Build and populate warehouse tables: Deploying the build and extraction scripts results in the creation and initial population of the warehouse tables.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Configuring for Physical Implementation

• Specify physical characteristics of generated objects, for example:– Indexes– Tablespace– Partitions

• You can configure, validate, and deploy objects individually in succession or all objects simultaneously.

Configuring for Physical ImplementationOWB generation scripts create database objects by using the physical characteristics that you specify in each object’s configuration dialog box.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Accessing Object Configuration

Accessing Object ConfigurationYou can access an object configuration either by right-clicking the object and selecting Configure or by highlighting an object and clicking the Configure icon on the toolbar.Configuring Objects to Be DeployedUntil now you have been defining logical objects in the staging area warehouse module.Before using OWB to generate and run scripts to create and populate database objects, you specify physical configuration settings for these objects.Configuring a TableIn most cases, the default values are appropriate.The only physical storage specification that is available in this slide’s example is the tablespace name.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Deployment Concepts

• The deployment step creates code from the logical models and stores this code in the Oracle database.

• The same code is stored in the run-time repository.

Deployment ConceptsWhat Deployment Does?

• The deployment step creates code from the logical models and stores this code in the Oracle database. For objects, you get data definition language (DDL) scripts; formappings, you get (mostly) PL/SQL scripts; and for process flows, you get XPDL (XML Process Definition Language) scripts. Apart from storing the code in the database, the same code is also made known in the run-time repository, so you can use Warehouse Builder to execute it.

• Location: Locations are physical places where source data is stored or Warehouse Builder objects are deployed. A location object stores all the information needed to access that place, including the encrypted credentials. It can refer to an Oracle database or a third-party database, a file system directory, a SAP application server, and so on.

• Registering a location: Registering a location establishes a link between the Warehouse Builder repository and the locations of source data and deployed objects.

• Connector: The way one location (or schema) is connected to another location (or schema/directory) owned by the target location. These connectors can become:

- Schema reference (from target schema to source schema)- Database link (from target schema to source schema)- Oracle directory (from target schema to source schema)

Note: The deployment step automatically performs a generate operation.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Registering Locations

Registering LocationsWhen you register locations, you specify the physical connection information that will be used during deployment to connect to the various data sources and targets.All modules must have locations assigned to them in order for them to be used during deployment. This includes the target as well as any sources or files.Note: Registration happens the first time when you use the location during a deployment. The same connection information is used for future deployments unless you change it. Registration Steps

1. In the Control Center Manager, select a location from the navigation tree on the left.2. Select File > Register. You can also right-click the location and select Register. The

Location Registration window appears. Depending on the type of location, there are different connection information requirements.

3. Enter the location registration details, and click OK to return to the Control Center Manager.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Unregistering Locations

Unregistering LocationsIf you want to delete a registered location, you must first unregister the location in the Control Center Manager and delete it from the Connection Explorer in the Design Center.Steps to Unregister a Location

1. In the Control Center Manager, select a location from the deployment tree.2. Select File, and then select Unregister. You can also right-click the location and select

Unregister. The Warehouse Builder Warning window appears. Click Yes if you want to unregister the location.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Configuration and Control Center

• Each project comes with a default configuration (DEFAULT_CONFIGURATION).

• Each configuration has an associated control center (DEFAULT_CONTROL_CENTER).

Configuration

DEFAULT_CONFIGURATION

Control centerDEFAULT_CONTROL_CENTER

OWB creates this for you by default.

1

1

Configuration and Control CenterConfiguration and control centers have the same relationship as that of a module with a location. The module is associated with a location. Similarly, each configuration is associated with one and only one control center. Each project comes with the default configuration (DEFAULT_CONFIGURATION), which, in turn, is associated with a control center (DEFAULT_CONTROL_CENTER). With Warehouse Builder, you can define multiple named configurations for the same set of objects. Use this if you are deploying the same system into multiple environments, such as Development and Test. Each configuration has an associated control center taking care of deploying to the correct environment.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Active Configuration

Two options to set a configuration as active configuration:

Option 1

Option 2

Active ConfigurationThe current active configuration is displayed on the status bar of the Design Center window.You can select from one of the two options if you want to set a configuration as active configuration.Option 1: In the Project Explorer, expand CLASS_PROJECT > Configurations. Right-click DEFAULT_CONFIGURATION, and select Set As Active Configuration. Notice that the active configuration on the status bar changesOption 2: In the Project Explorer, expand CLASS_PROJECT > Configurations. Double-click DEFAULT_CONFIGURATION. Click the Name tab, and select “Set and save as my Active Configuration for this project.”

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Control Center and Locations

Locations

Locations

Locations

Control Center and LocationsControl centers are visible in the tree in the Connection Explorer panel. Locations are assigned to a control center. One location can be in one ore more control centers. Just like locations, control centers are also shared across projects. Control centers know about locations when you assign the locations to the control center. A configuration is associated with a control center. You deploy objects to a control center. To deploy objects to a particular control center, ensure that the configuration associated with that control center is set as Active.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Control Center Manager Components

Deployment tree

Control Center Manager ComponentsThe Control Center Manager is a central graphical facility that enables you to view and manage all aspects of objects. You use the Control Center Manager to deploy objects to explicitly register locations, to start mappings, and so on. The Control Center Manager always opens up in the context of the active configuration, which determines the control center. In the Control Center Manager console, you can access design objects according to their locations. The navigation tree is organized locationwise. Control Center Manager Components

• In the Control Center Manager, on the left, is the deployment tree with the current project displayed.

• Object Details displays a summary of information relevant to the object or set of objects selected in the deployment tree.

• Control Center Jobs displays the deployment status.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Invoking the Control Center Manager

Invoking the Control Center ManagerTo launch the Control Center Manager, in the Design Center, from the Tools menu, select Control Center Manager.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Control Center Manager Interface

Control Center Manager InterfaceSelecting Objects for DeploymentThe Control Center Manager window displays a collapsed view of the project tree in the left pane. Expand the project to display the contents. Note that the project tree consists of locations that you have defined. You can choose to deploy:

• Selective objects within one or more locations• All objects within one or more locations• All objects within the project

When you select an object or a set of objects that you want to deploy, the details about the object or objects appear on the Details tabbed page in the Object Details window. To deploy, select an object for deployment, and click the Default Actions button. This changes the deploy action for each object to a default value. If the object has not been previously deployed, the default value is “Create.” Repeat this step for all objects that you want to deploy. Special icons are displayed in the deployment tree next to the objects that are selected for deployment.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Default Action and Deploy

The Default Actions button changes the deploy action from None to Create.

Deploy

Default Action and DeployDefault Action ButtonWarehouse Builder provides a certain degree of deployment “intelligence.” The Default Actions button changes the deploy action from None to an action based on the object’s prior deployment history. In this instance, where these tables are being deployed for the first time, the default action is set to Create.Deploy ButtonClick the Deploy button on the toolbar to begin the process of generating and deploying the scripts to create the tables in your target schema.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Deploy Options

Deploy OptionsOracle Warehouse Builder 10g Release 2 provides a number of deploy options:

• You can specify whether or not you want to see a commit prompt before deployment. (If you deselect the option, Warehouse Builder automatically commits.)

• You can specify whether or not you want to see the intermediate generation results before deployment.

• You can specify whether or not you want Warehouse Builder to help you identify dependent objects for your deployment. (For example, if you deploy a mapping, then the dependent objects may be the tables you included in the mapping.)

• Warehouse Builder can generate a job name for you. However, if you want to explicitly specify the job name, you enable the Job Name Prompt option.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Asynchronous Deployment and Execution

Deploymentmanager

-Deploy- Wait

- Execute- Wait

- Deploy- Wait

and so on

Pre-OWB 10g R2synchronous

OWB 10g R2 asynchronous

Control Centermanager

- Deploy- Execute - Deploy- Coffee- Executeand so on

- Coffee- Wait

- Coffee- Wait

- Coffee- Wait

- etc.

Processesrun on serverasynchronously.

Asynchronous Deployment and ExecutionIn older releases of Warehouse Builder, you would always perform the so-called synchronous deployment and execution through the deployment manager. A busy bar would appear on the screen and stay there until the deployment or execution has finished. Oracle Warehouse Builder 10g Release 2 provides asynchronous deployment and execution—you can submit a deployment or execution process, and the deployment or execution process runs on the server. In the meantime, you can continue working with Warehouse Builder or even shut down the client without interrupting the deployment or execution that was submitted. Note that code generation is synchronous and still takes place on the client.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Deployment Tools Preferences

Deployment Tools PreferencesOracle Warehouse Builder 10g Release 2 provides a set of preferences that help control the usability of the Control Center Manager. To launch the Preferences dialog box, in the Design Center, from the Tools menu, select Preferences. The Preferences dialog box is launched.The left panel of this dialog box lists the types of preferences. Click a preference type in the left panel to display its preferences in the right panel. The right panel contains the preference name and the values that you can set for the preference.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Deployment Process Preferences

Deployment Process PreferencesThe preferences under Deployment Process enable you to set the following preferences:

• Specify whether or not to show a deployment completion message (in the context of asynchronous deployment).

• Specify whether or not to pause after the code generation.• Specify whether you want to be asked for a job name. Warehouse Builder generates a

default job name if you do not specify one explicitly.• Warehouse Builder requires you to commit any changes before you perform a

deployment process. The “Prompt for commit” preference enables you to control whether you want to confirm the commit message or whether you trust the automatic commit.

• “Prompt for execution parameters” is the preference that enables you to control whether you get the execution parameters dialog box prompting for the parameters.

• Allow Undo/Redo is an option that controls whether you want to enable the undo or redo action in the context of generating upgrade scripts.

• The Show Monitor option controls whether or not you want to show the job monitor.Note that some of these preferences are available as options in the Control Center Manager itself. The main difference is that the options are not stored, whereas the preferences are stored and retrieved the next time when you use Warehouse Builder.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Deploying Objects

For this course, follow this order to generate and deploy objects to the SALES_WH target schema.

Sequences

Tables

Dimensions

Cubes

Mappings

Process flows

Deploying ObjectsAfter you have provided OWB with the design, you generate scripts and deploy them to theSALES_WH target schema. You generate both these scripts:

• DDL scripts to create the objects (sequence, tables, dimension, cube, and so on)• DML scripts according to the mappings (in the form of stored procedures)

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Deploying Sequences

Deploying SequencesFor this course, you first deploy sequences. To deploy sequences, perform the following steps:

1. In Control Center, expand SALES_WH_LOCATION > SALES_WH > Sequences. In the Object Details panel, all sequences under the SALES_WH module are listed.

2. At the lower-right corner in the Object Details panel, click Default Actions. Notice that the values in the Deploy Action column changes from None to Create.

3. On the toolbar, click Deploy, or from the File menu, select Deploy > To Control Center. You see the deployment results on the Deployment tabbed page of the Control Center Jobs panel.

Note: You deploy other objects in a similar manner by selecting respective objects. For example, to deploy tables, expand SALES_WH_LOCATION > SALES_WH > Tables. Then perform steps 2 and 3.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Control Center JobsA job is a deployment or execution submitted to the control center.

You can double-click a job to see its details.

Generate Run

Completed successfully

Errors

Warnings

Status in the Control Center Jobs panel

Control Center JobsWith the introduction of asynchronous deployment, Warehouse Builder introduces the concept of a job. A job is a deployment or execution that is submitted to the control center. This includes executions that have a schedule associated with them. The jobs are exposed in a separate panel in the deployment manager. You can also invoke the Job monitor in a separate window.In the Control Center Jobs window, monitor the job status. Wait for the status to change from “Generate” to “Run” to “Completed successfully.”

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




OWB Automatically Creates a Connector

When a mapping’s source and target objects belong to different schemas,OWB automatically creates a connector in the target table’s location that references the source table’s location and that is instantiated at run time as a database link.

ConnectorDifferentschemas

OWB Automatically Creates a ConnectorConnector is created in the target location: As you create the table-to-table mapping, OWB automatically creates the SALES_WH_TO_XSALES connector as a node within the SALES_WH target location. The connector links this target location with the source location. A connector between two different schema locations is instantiated as a database link.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Loading the Target WarehouseControl centre

Locations

Designrepository

Loading the Target WarehouseIn Oracle Warehouse Builder, you can execute two types of deployed objects:

• Mappings • Process flows

After you deploy process flows or mappings to your target system, they are available for execution from within the Control Center Manager.Typically, you want to load a target warehouse with data and subsequently perform data refreshes. Either you can execute the extract, transform, and load (ETL) mappings individually each time you want to load or reload data or you can execute a process flow. The process flow automates the order and dependency of the mappings execution. The process flow also enables you to specify what action to perform when the mappings execution ends in error, ends with a warning status, or completes successfully. In this lesson, you execute the deployed process flow and also view the loaded data in the Data Viewer.To load data into the target dimensions and cube, you need to execute the process flow. The process flow automatically invokes the mappings to load the dimensions and the cube.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y













9. View the data.

Course Progress ReportAfter deploying objects, you are now ready to execute or start mappings. This step loads data into dimensional objects.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Executing Mappings

Executing MappingsTo execute mappings, perform the following steps:

1. In the Control Center Manager, expand SALES_WH_LOCATION > SALES_WH > Mappings.

2. Select the mapping you want to execute.Note: You need to first execute the mappings that load the dimension and then execute the mapping that loads the cube.

3. Click the Start button on the toolbar, or select Start from the File menu.Note: This is to show you how to execute a mapping. In a real-life scenario, you do not execute individual mappings; instead, you use process flows.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Executing the Process Flow

Executing the Process FlowTo execute the process flow, perform the following steps:

1. In the Control Center Manager console, expand OWF_LOCATION > MY_PF_MODULE > PK. Select LOAD_SALES_WH.

2. Click the Start button on the toolbar, or select Start from the File menu.The Control Center Jobs panel in the lower-right portion switches to the Execution tab. You can monitor the execution in this panel. After the execution is successful, double-click LOAD_SALES_WH in the Job column of the Control Center Jobs panel.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Execution Window

Execution WindowIn the LOAD_SALES_WH dialog box, click the Execution Results tab and monitor the row activity. You can get a count of how many rows are inserted in respective dimensions and the cube. On the successful execution of the process flow, all the dimensions and the cube are now loaded with data.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y






2. Ensure the data quality using data profiling.







9. View the data.

Course Progress ReportAfter executing the mappings that load data into the objects, you are now ready to view the results of your work.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Viewing Data Using the Data Viewer

Viewing Data Using the Data ViewerYou can view the data loaded in the dimensions and the cube from within the Oracle Warehouse Builder design client environment by using the Data Viewer.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 10-1: Deploying, Loading,and Viewing Data

This practice covers the following topics:• Deploying the target warehouse• Loading the target• Viewing the data by using the Data Viewer

Practice 10-1: Deploying, Loading, and Viewing DataAfter working on the design for quite a while, you are now ready to place the design onto the database. In this practice, you deploy all the relational and dimensional objects you previously created, and also deploy the ETL mappings and the process flow you designed. You then execute the process flow and load the data by using the Data Viewer.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Managing Metadata Using Dependency Manager

Proactively manage change in your system.

Managing Metadata Using Dependency ManagerIn this topic, you learn how to manage your metadata by using the Dependency Manager in Warehouse Builder. The Warehouse Builder Dependency Manager enables you to determine the impact of the changes made to the object definitions or the metadata in the Warehouse Builder repository. The Dependency Manager enables you to plan your project by previewing the impact of the changes or future changes. If you are planning to introduce changes to your source systems, you can use the Dependency Manager to gauge the impact of that change on your warehouse design. Or, if the change has already been introduced, you can plan the time required to update your ETL design and rebuild your data warehouse.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Integrated Lineage and Impact Analysis

The Dependency Manager is part of the design client.Benefits:• Usability: A rich-client user interface provides a

powerful environment for dependency analysis.• Completeness: End-to-end lineage and impact

analysis supports full business intelligence environment.

Integrated Lineage and Impact AnalysisOracle Warehouse Builder 10g Release 2 introduces a major visible component for metadata management: Dependency Manager.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Invoking Lineage and Impact Analysis

• Right-click any object in thenavigation tree.

• Choose one ofthe following:– Lineage – Impact

Invoking Lineage and Impact AnalysisWhat Is Lineage and Impact Analysis?Lineage and impact analysis (LIA) diagrams show the relationships among objects managed by Warehouse Builder. These relationships are constructed by mappings and process flows. The lineage diagram for a particular object shows its source objects, and the impact diagram shows its targets.To Generate a Diagram by Using the Design Center:

1. Expand the Project Explorer until you see the object that you want to analyze. 2. Right-click the object, and select Lineage or Impact from the pop-up menu. The

Metadata Dependency Manager opens with the diagram. To Generate a Diagram by Using the Metadata Dependency Manager:

1. From the Design Center Tools menu, select Metadata Dependency Manager. The Metadata Dependency Manager is displayed.

2. Expand the DM Context Tree until you see the object that you want to analyze. 3. Right-click the object, and select Show Lineage or Show Impact from the pop-up

menu. The diagram is displayed on the canvas.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Lineage AnalysisThe lineage diagram for a particular object

shows its source objects.

Lineage AnalysisTo know where the information in the SALES cube has come from, click the (+) symbol to the left of the SALES cube to show more details from a lineage perspective. The diagram expands tracks back to the first level of all the data objects that are directly related to SALES.Note: The (+) sign to the left of each operator gives the dependency detail from the lineage perspective. It shows the details about all the objects that the object (SALES) is dependent on. Data Flow Between ObjectsThe (+) symbol between the ORDER_ITEMS table and the SALES cube indicates that there is a mapping piece. Double-click the (+) symbol. You are now able to get an overview of thedata flow.The Dependency Manager not only includes the lineage and impact analysis information between data objects, but also the data flow (information) between those objects.Calculating Impact and Lineage at the Attribute LevelDouble-click the Aggregator operator to see details about the attribute level.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Impact Analysis

The impact diagram for a particular objectshows its targets.

Impact AnalysisIn the slide, you see the Impact Analysis diagram for the SALES cube. The (+) sign on the right of the operator provides details about the objects that will be impacted as a result of change. The Impact Analysis diagram displays all the objects that will be affected as a result of change made to the cube operator. The Dependency Manager enables you to plan your project by previewing the impact of the changes or future changes.To generate a diagram from the Design Center:

1. Expand the Project Explorer until you see the object that you want to analyze. 2. Right-click the object, and select Impact from the pop-up menu. The Metadata

Dependency Manager opens with the diagram.O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Tree View

Tree ViewThe Dependency Manager also provides a tree panel that you can use to add objects to the dependency graph. To enable the tree panel, from the Window menu, select Tree View.Expand the project in the DM Tree panel. You can drag objects anywhere on the canvas and the graph is recalculated.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




User-Defined Objects and Icons

• User-definable:– Objects– Associations– Properties

• Leverage custom icons for easy recognition.

• Access full metadata services of OWB (for example, impact analysis).

User-Defined Objects and IconsUsing Warehouse Builder, advanced users define their own object types in the Warehouse Builder repository like the regular Warehouse Builder objects. For example, a user defines an object type called “Report,” which is based on another object type called “query.” Regular users can now create instances of this object type within the Warehouse Builder client and define relationships between them just like any other Warehouse Builder objects.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating an Icon Set

Creating an Icon SetIcons are graphics that visually suggest the availability of a function or type of an object to a user. There are many types of objects predefined inside OWB, each with their own icon. Oracle Warehouse Builder 10g Release 2 supports user-defined objects, and with these, users may want to change the default icon to something representative of the object.You learn how to define your own icons and associate them with existing OWB objects or your own user-defined objects. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Using an Icon Set

Using an Icon SetIn this section, you learn how to use an icon set.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




User-Defined Objects

User-Defined ObjectsSee an example to use Warehouse Builder in conjunction with other applications. See how the data and metadata that you manage in Warehouse Builder interacts with other applications. You can introduce new metadata objects into the Warehouse Builder repository and associate those objects with existing Warehouse Builder objects. Warehouse Builder displays these custom objects in the Design Center with the icon of your choice, and includes the objects in lineage and impact analysis reports.Administration users can extend the Warehouse Builder repository by adding new objects to the repository. You can introduce new objects to the repository by defining user-defined objects (UDOs), which follow Warehouse Builder rules for object locking, multiuser access, transactions, security, and snapshots. You can also import and export UDOs by using the Metadata Loader (MDL).

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Repository Browser

An HTML-based interface to view and generate reports on all repository metadata objects and the relationships between those objects

Repository BrowserThe repository browser is the central reporting tool for viewing the data and metadata stored in the Warehouse Builder Repository. This includes lineage and impact reports on all objects in the Warehouse Builder projects as well as run-time data that records information about deployments and executions.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Starting the OWB Browser Listener

Starting the OWB Browser ListenerTo start the stand-alone version of the repository browser, you must start the OWB Browser Listener. To start the OWB Browser Listener, from your desktop, select Start > Programs > (your Oracle – OWBclientHome) > Warehouse Builder > Administration > Start OWBBrowser Listener. A command window opens. Do not close this window. Minimize it.Note: You need to run only one instance of the OWB Browser Listener in your enterprise. Then anyone with the login credentials and a Web browser can access OWB repository reports, without the need to have the OWB Client installed.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Logging In to the Warehouse Builder Browser

Logging In to the Warehouse Builder BrowserTo start the repository browser, perform the following steps:

1. From your desktop, select Start > Programs > (your Oracle – OWBclientHome) > Warehouse Builder > Repository Browser. A browser window appears.

2. In the browser window, enter the login details: UserName: rep_owner Password: rep_ownerHost Address: localhostHost Port Number: 1521 (already set)Host Service Name: Your specified database name

The following are the two types of reports that you can browse in the repository browser: • Design Repository reports give you the design details about all the objects present in

your OWB project.• Control Center reports help you examine the deployment and execution details about

your objects. You begin analyzing the Design Repository reports. Select Design Repository, and click Login.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Browsing Design Repository Reports

Viewing ReportsIn the Navigator, you can navigate into your projects in the unified repository and explore details about the objects inside the project. Expand rep_owner, and then expand CLASS_PROJECT. You get a view of all the modules. Expand SALES_WH and you get a listing of all the objects contained in the module.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Browsing Control Center Reports

Browsing Control Center ReportsTo browse Control Center reports, you do not need to go to the Login page again. To switch over to Control Center reports, scroll down on the same page, and click Control Center: Reports in the Related Links section in the lower portion of the page.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Types of Control Center Reports

Types of Control Center ReportsThe reports are categorized into deployment, execution, and management reports. If you want to know the current deployment status of all the objects, click the Object Summary Report link in the Deployment section of the Reports page.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Object Summary Report

Object Summary ReportOn the Object Summary Report page, you see useful deployment details about each object. From the report, you know the date and time when the SALES cube was deployed, the location it was deployed to, and whether the deployment was Valid.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Execution Summary Report

Execution Summary ReportThe Execution Job Report shows the details about the execution of the LOAD_EXPENSE_WH process flow. The execution status is marked as Complete: OK. (The results may vary depending on your success with the practice). You can drill down into the details of the execution by clicking Execution Job Report in the Related Information column of the table.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Summary

In this lesson, you should have learned how to:• Use the Control Center Manager• Load data into the tables• Use the Dependency Manager to manage metadata• Describe user-defined objects

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 10-2: Metadata Management

This practice covers the following topics:• Managing metadata by using the Dependency

Manager • Administering the warehouse by using the

repository browser

Practice 10-2: Metadata ManagementIn this practice, you learn how to use the Oracle Warehouse Builder Dependency Manager, a graphical interface that displays how changes in your sources impact the design metadata in your repository. You also learn how to use the Oracle Warehouse Builder repository browser, an HTML-based interface, to view and generate reports on all repository metadata objects and the relationships between those objects.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y



Business Intelligence Integration

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Objectives

After completing this lesson, you should be able to do the following:• Define Oracle Discoverer structures• Derive Oracle Discoverer structures based on a

dimensional model • Define the cross-tab and graph presentation

templates of Oracle Business Intelligence Beans presentation templates (Deployment is not discussed.)

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Business Justification: Tools Integration

• By implementing a new concept of business intelligence objects, OWB can be integrated with reporting environments more seamlessly.

• OWB becomes more of a business intelligence factory as it integrates with more tools.

Discoverer

BI Beans

Business Justification: Tools IntegrationTools integration is a key phrase in Oracle’s business intelligence message. Customers spend much time and money in integrating the best tools.Oracle Warehouse Builder (also called as Warehouse Builder or OWB) is increasingly becoming the center of business intelligence design and definition.Integration with reporting tools enables easier development of business intelligence information systems.Business Definitions for Discoverer and BI BeansThe Business Intelligence node in the navigation tree enables you to define sets of Warehouse Builder objects that contain business-reporting tools, initially Oracle Discoverer and Oracle Business Intelligence Beans (BI Beans). These business intelligence definitions are deployed to the target reporting environment after they are configured, validated, generated, and deployed by the Warehouse Builder client.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Integration with Discoverer

• Old method: – In OWB, create a collection and run an export bridge that

generates an .eex file.– Import the .eex file into Discoverer.

• New method:– Deploy objects directly into Discoverer EUL.– Discoverer Bridge is no longer used.

• Benefits:– Completeness: BI design in Warehouse Builder– Productivity: Control Discoverer deployments– Completeness: No need for Discoverer customizations– Productivity: Direct building of reports based on

Warehouse Builder design by end users– Manageability: Known impact on Discoverer objects

Integration with DiscovererOld Method: Export and ImportTraditionally, metadata integration between Oracle Warehouse Builder and Oracle Discoverer involved creation of an export file in OWB and then its import through the Discoverer Administrator. New Method: Deploy Directly into DiscovererOracle Warehouse Builder 10g Release 2 introduces object definitions that represent objects in the Discoverer End User Layer (EUL). The objects can be designed (or derived, based on data object definitions), and then deployed into Oracle Discoverer. Benefits

• When using OWB as a starting point, Discoverer Administrator is not needed to re-create the environment if changes come in or if a new environment must be rolled out.

• Warehouse Builder lineage definitions and impact analysis services can be extended to Discoverer EUL objects.

• You can leverage Warehouse Builder’s metadata management controls, including version control and multilanguage support.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Two Ways to Define Discoverer Objectsin Warehouse Builder

Building definitionsmanually

Deriving definitions from a set of objects or a collection

Two Ways to Define Discoverer Objects in Warehouse BuilderYou can choose between two paths for defining the Discoverer objects in Warehouse Builder:

• Manual definition• Derivation

When you derive a business area definition from a collection, you can get it “for free.” The following pages show an example of manually defining a business area, and then deriving definitions from existing Warehouse Builder objects.Discoverer Version CompatibilityThe Oracle Warehouse Builder 10g Release 2 API works with Oracle Business Intelligence Discoverer 10.1.2. If your target is an earlier version of Discoverer, export an .eex file and import it into Discoverer Administrator to create an EUL.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating a Business Definition Module

Business Definitions module contains:– Item Folders (module level)– Business Areas

– Item Folders (business area level)– Drill Paths– Lists of Values– Alternative Sort Orders– Drills to Detail– Registered Functions

Examined inthis lesson

Creating a Business Definition ModuleThe first of two approaches to defining Discoverer objects in OWB involves manually defining definitions.At the highest level under Business Definitions, you define a module to contain your definitions.The creation of business definition modules for Discoverer is wizard driven. In this wizard, you simply name the business definition module and choose or create a location.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating a Business Area

Creating a Business AreaWithin the business definitions module, you create a business area. Business area creation is also wizard driven. The wizard consists of two steps:

1. Name the business area.2. Select the business area folders.

The language to deploy is controlled by the “MLS Deployment Language” Configuration property in the Configuration details for the business definition module. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Creating a Simple Item Folder

Defining an item folder at the module level

(Defining an item folder at the SALES_DATAbusiness area level)

Business Definitions module contains:– Item Folders (module level)– Business Areas

– Item Folders (business area level)– Drill Paths– Lists of Values– Alternative Sort Orders– Drills to Detail– Registered Functions

Examined in this lesson

Creating a Simple Item FolderNow that you have created a business area in your business definition module, you create an item folder for the business area.Note: There are two nodes available for defining item folders. One is at the lower business arealevel (SALES_DATA). The other is at the higher business definition module level (DISCOVERER_OBJECTS). For this example, you create an item folder at the higher module level. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly





1. Rename asSALES_PROMOTIONS.

2. Right-click header andselect Detail View.

Creating a Simple Item Folder (continued)The Data Object Editor opens with an item folder having the default name ITEM_FOLDER_1. In the Name field in the lower-right panel, rename the item folder as SALES_PROMOTION. Then right-click the header on the canvas, and select Detail View.Simple Versus Complex FoldersWarehouse Builder distinguishes simple item folders from complex item folders in the same way as Discoverer does. A simple item folder is directly based on a table, without any calculations. A complex item folder can contain items as well as calculations from multiple other item folders.You first create a simple item folder.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y





Creating a Simple Item Folder (continued)Drag the Table icon from the Data Object Editor Palette onto the canvas. The Add a New or Existing Table dialog box appears. Expand Tables. Expand the SALES_WHmodule, and select the PROMOTIONS table. Click OK.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y





Drag the Columns headerof the PROMOTIONStable to the Items node of theSALES_PROMOTIONSitem folder.

Creating a Simple Item Folder (continued)Place the PROMOTIONS table to the left of the SALES_PROMOTIONS item folder.Drag the Columns header of the PROMOTIONS table to the Items node of the SALES_PROMOTIONS item folder. This brings all the columns from the table into the item folder. Close the editor.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating a Drill Path

Creating a Drill PathA drill path primarily defines a hierarchy relationship in a dimension.Besides creating drill paths manually, you can use a wizard to create Drills to Detail. Alternatively, if you derive a dimension, you get the drill path automatically.In the DISCOVERER_OBJECTS folder, you create a new drill path, PROMOTIONS_DRILL.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Deriving Individual Objects

Multiselect the dimensionsand cube from which youwant to derive businessdefinitions.

Deriving Individual ObjectsUndesirable Duplication of MetadataAs you define the database (relational or OLAP) and load data into it, you create and collect a lot of metadata. Traditionally, you then build an application on top of this database design, duplicating the work of creating metadata and designs all over again.Eliminating Duplication by Deriving End-User Metadata from the DesignOracle Warehouse Builder 10g Release 2 eliminates this duplication of effort and metadata byderiving the end-user metadata from your design. This not only reduces the work required, it also reduces the risk of errors and metadata synchronization requirements, thus increasing your metadata quality. OWB Enables Impact Analysis of Discoverer ObjectsBy having metadata definitions in one place, you can deliver end-to-end impact analysis. Not only can you determine up front, the impact of changes on your database, you can also determine the impact on your business intelligence environment.In Oracle Warehouse Builder 10g Release 2, you can, for example, select your cube metadata and derive an Oracle Discoverer EUL. Then store this information in the Warehouse Builder repository. You can then edit the Discoverer objects within Warehouse Builder. After you are satisfied with the results, you simply deploy this information to Discoverer.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Selecting Target and Rules for Derivation

Selecting Target and Rules for DerivationSelecting Target for DerivationIn step 2 of the wizard, you select the target structure that will receive the business objects derived from the dimension and cube definitions. In this example, you select the SALES_DATAbusiness area located in the DISCOVERER_OBJECTS business definition module.Selecting Rules for DerivationEach derivation session may require parameters. Using the drop-down list for rules, you select Global, Table, or Dimension. With the drop-down list for log level, you choose Errors only, Warning, Information, or Debug trace.In this example, you do not change any of the default rules.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Examining Derived Business DefinitionsFor dimensions andcubes, OWB createsDiscoverer objects:• Simple item folders:

• Are based on columnsfrom single tables thatimplement dimensionsand cubes

• Are not visible to users• Complex item

folders:• Can reference folder

items of other folders• Can contain

calculations• Are on top of simple

item folders• Are visible to users

• Drill paths:• Are used to implement

dimension hierarchies

Examining Derived Business DefinitionsOpen the SALES_DATA business area. Verify that the tree shows the derived definitions. Warehouse Builder distinguishes simple item folders from complex item folders in the same way as Discoverer.Simple Item FoldersA simple folder contains folder items that are based on columns from a single table, without any calculations. Warehouse Builder creates hidden simple item folders on top of the relational tables that implement dimensions and cubes.Complex Item FoldersIn Discoverer, a complex folder can contain folder items that refer to related folder items within other folders. Complex folders can also contain calculations. For dimensions and cubes, Warehouse Builder creates complex item folders visible to the users, on top of the simple item folders.Drill PathsThe derivation process also creates drill paths that implement the respective hierarchies on the dimensions. Finally, because you selected a business area as a target, all item folders are referenced by that business area.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Deriving from a Collection

1. Create a new BusinessDefinitions module as the derivation target.

A collection can be a source for deriving a business area that contains item folders.

2. Create a SALES_MARTcollection.

Deriving from a CollectionWith Oracle Warehouse Builder 10g Release 2, you can derive objects in two ways:

• Derive sets of individual data objects• Derive a grouping of data objects in the form of a collection

Collections Can Be Derived into Business AreasYou can derive a business area from a collection, and the resulting business area will contain item folders. Basically, you use the same model as Discoverer:

• You can have item folders in general.• You can have item folders referred to as being one or more business areas.

Warehouse Builder supports this model. By selecting the module instead of the business area as a target (if you derive individual design objects), you get one of the following:

• The item folders on the higher level• The reference in the business area included

You just derived business objects from five individual dimensions and a cube. You now create a collection, and then derive business objects from that collection.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Deriving from a Collection

Deriving from a Collection (continued)In this example, the SALES_MART collection comprises the CHANNELS and PRODUCTSdimensions and the SALES cube.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating a Complex Item Folder

Can change defaultaggregate from SUM to MAX, AVG, COUNT, and so on.

Can create calculationsfor an item

Uses items from other item folders

Creating a Complex Item FolderYou can create a complex item folder whose source items come from other item folders. You can use the Expression Builder graphical interface to create calculations for items. You can change item properties. (For example, the screenshot in the lower portion of the slide shows the default aggregate being changed from SUM to MAX). In the next practice, you define a PRODUCT_SALES complex item folder with items from the PRODUCTS and SALES item folders. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Creating a List of Values

1. Select item that defines LOV. 2. Select items that reference LOV.

Creating a List of ValuesYou can create a list of values (LOV) to restrict information to one or more items selected from that list. For example, if you create an LOV for all products, a report can be restricted based on items selected from the list of products.A wizard is available to create an LOV. The wizard guides you in selecting the item that defines the LOV, and the items that reference the LOV. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Creating Drill to Detail

Specify “Drill to Detail” in the list of values definition.

Creating Drill to DetailNow your manager wants to drill down on the specifics of the product for details. To enable this functionality for an item, you can create Drill to Detail and relate the item to that Drill to Detail.Currently, each of the following constructs materializes as an item class in Discoverer:

• List of Values• Drill to Detail• Alternative Sort

However, Discoverer allows only a maximum of one item class per item. Therefore, to enable Drill to Detail on the item class that will implement your PRODUCTS_LOV list of values, you must edit the PRODUCTS_LOV list of values.Using the Check Box in List of ValuesThere is a check box to set this list as Drill to Detail. When you deploy the object definitions to Discoverer, the item class that is created contains both List of Values and Drill to Detail.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 11-1: Defining Business Intelligence Objects Based on Data

ObjectsThis practice covers the following topics:• Defining Discoverer structures• Deriving Discoverer structures based on a

dimensional model

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Generating and Deployingthe Intelligent Objects

Generating and Deploying the Intelligent ObjectsUntil now you created the business definition module to hold the item folders and the drill paths. You also created the business area that contains the item folders. After creating the objects in OWB, you deploy the item folders, the drill paths, and the business area. Now you deploy the business area in OWB for use in Discoverer Administrator. The deployment will be successful only if you have already created an EUL in Discoverer Administrator. After successful deployment, you can view the business area in Discoverer Administrator. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Analyzing Data Using OracleBI Discoverer Components

OracleBI Discoverer Viewer Relational/OLAP

OracleBI Discoverer Plus Relational

(used in next practice)

OracleBI Discoverer Portlet Provider

OracleBI Discoverer Plus OLAP

Analyzing Data Using OracleBI Discoverer ComponentsThe Oracle Business Intelligence Suite CD contains four components of the OracleBI Discoverer product offering.OracleBI Discoverer Plus OLAP and OracleBI Discoverer Plus RelationalOracle Database 10g provides analytic services for both multidimensional and relational data sources. OracleBI Discoverer Plus enables users to create reports, perform ad hoc querying, and engage in sophisticated analysis of multidimensional and relational data sources.

• Discoverer Plus OLAP can be used against multidimensional data and data warehouse schemas in star or snowflake form.

• Discoverer Plus Relational (used in next practice) works against any relational schema.OracleBI Discoverer ViewerEnd users and data analysts can view, navigate, and analyze reports that are created with Discoverer Plus OLAP and Discoverer Plus Relational. Because reports are presented in pure HTML format, Discoverer Viewer requires no software other than a Web browser.OracleBI Discoverer Portlet ProviderDiscoverer users can also publish Web versions of Discoverer Plus reports by using Discoverer Portlet Provider.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Connecting to Discoverer Plus Relational

Connection manager

After generating anddeploying the businessarea, examine it inDiscoverer.

Connecting to Discoverer Plus RelationalConnection ManagerTo display the Discoverer Plus connection window, enter the URL for Discoverer Plus in the address field of your browser. The URL uses the following format:

http://<app_server_host name>:<port number>/discoverer/plusIn the Discoverer Plus connection window, select OracleBI Discoverer, enter the appropriate connection authentication information, and then click Go.Examining EUL in DiscovererAfter generating and deploying the business area, you can look at the EUL in Discoverer.After the Discoverer objects are deployed from Warehouse Builder, end users can start defining their reports in Discoverer Plus.You can truly design your EUL in Warehouse Builder, gaining the advantages of redeployment, impact analysis, and lineage.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Examining EUL in Discoverer

SALES_DATA

Dimensions and cubesare derived into complex folders, and their bound tables are simple folders.

Examining EUL in DiscovererIn the resulting Discoverer EUL, dimensions and cubes are derived into complex folders, whereas their bound tables are derived into simple folders.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Examining EUL in Discoverer

SALES_DATA

Hierarchies are alsoderived and deployed.

If changes are made later, you can rederive the definitions.

Examining EUL in Discoverer (continued)Hierarchies defined in Warehouse Builder as drill paths are also derived and deployed. It is expected that Discoverer will eventually adopt the same terminology of “drill path.”RederivingBecause business intelligence systems are inherently dynamic, change may come from the sources or from end users. As a result, business definitions will be impacted.Warehouse Builder supports the concept of rederive so that you can select a definition and derive it again.If you already made changes to the business definition itself, make sure you select the option to preserve the user changes in the derivation parameters.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Practice 11-2: Deploying OWB Business Intelligence Objects to a Discoverer End

User LayerThis practice covers the following topics:• Creating an End User Layer in Discoverer

Administrator• Generating and deploying the business area in

Warehouse Builder• Examining the OWB-generated EUL results by

using Discoverer Plus Relational

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Integration with BI Beans

Old: No prior capability in Warehouse Builder to predefine objects for BI Beans New: Deployment of a default BI Beans cross-tab or graph report stored in a BI Beans catalog, referencing the metadata in the OLAP catalogBenefits:• Productivity: Quick start to BI Beans definition• Manageability: Changes propagated to BI Beans

definitions• Analysis: Full impact and lineage analysis

Integration with BI BeansOracle Warehouse Builder 10g Release 2 introduces the ability to define the skeleton for cross-tabs and graphs inside Oracle Warehouse Builder. These definitions can be implemented as Oracle Business Intelligence Beans (BI Beans). The skeleton reports can be directly used by end users to look at the data. In this way, you can quickly and effortlessly show data in an application to your end users, allowing them to drill down and pivot. Because the report definition is stored in the BI Beans catalog, you can later on build on top of this first-cut application.Rapid PrototypingThis method is ideal for prototypes that quickly need a BI Beans definition, but it can also provide a head start for the development of a BI Beans application. These applications can be used to provide end users an early view of the queries that they will be able to develop.Impact and Lineage AnalysisAnother major benefit of this approach is the full impact analysis and lineage analysis.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating a Business Presentation Module

Creating a Business Presentation ModuleThe definition of business presentations starts with the definition of the container that contains the presentations—the business presentation module.The Create Business Presentation Module Wizard enables quick creation of a report structure object.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Creating a Presentation Template

Creating a Presentation TemplateA wizard is provided to create the actual presentation template. This is the metadata definition for the template.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Selecting the Report Type

Selecting the Report TypeYou can select a cross-tab or graph report structure. For either report type, you can select a report subtype from among different subtypes.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Selecting the Items for the Report

Selecting the Items for the ReportOn this wizard page, you select a cube and its members, such as measures and referenced dimensions.Selection from one cube of one warehouse module is allowed. Selection of one hierarchy of a dimension is allowed.Selection of a cube brings along all its measures. If you select “Automatically add the dimensions and dimension roles,” the cube’s referenced dimensions are also selected. O

racl

e U

nive

rsity

and

Bus

ines

smin

d C

olom

bia

SA u

se o

nly




Specifying the Report Layout

Specifying the Report LayoutX and Y edge dimensions can be dragged from Page Edge Items. These relate to x/y for a cross-tab, bar/groups for a bar chart, and slices/groups for a pie graph.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Connecting to the BI Beans Report Viewer

After generating anddeploying the reportdefinition, you can examine it in the BI Beans Report Viewer.

Connecting to the BI Beans Report ViewerAfter generating and deploying the report definition in Warehouse Builder (not done hands-on in this course), you can invoke the BI Beans report viewer and authenticate yourself as the user to the BI Beans catalog. To deploy, you would need to define a location specifying a BI Beans catalog user for BI Beans.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Examining the BI Beans Report

Examining the BI Beans ReportThe contents of the catalog are shown. You can open up the first-cut skeleton report that you defined in Warehouse Builder.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Drilling Down into the Report

Drilling Down into the ReportThe report always opens at the highest level. You can drill down to the desired level.

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y




Summary

In this lesson, you should have learned how to:• Define Discoverer structures• Derive Discoverer structures based on a

dimensional model • Define BI Beans cross-tab and graph presentation

templates

Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


Ora

cle

Uni

vers

ity a

nd B

usin

essm

ind

Col

ombi

a SA

use

onl

y


Oracle Warehouse Builder 10g Implementation Part 1 · PDF fileOracle Warehouse Builder 10g:...

Documents

Transcript of Oracle Warehouse Builder 10g Implementation Part 1 · PDF fileOracle Warehouse Builder 10g:...