1 Copyright © 2009, Oracle. All rights reserved. Administrative Tasks in Warehouse Builder

1Copyright © 2009, Oracle. All rights reserved.

Administrative Tasks in Warehouse Builder

Copyright © 2009, Oracle. All rights reserved.1 - 2

Objectives

After completing this lesson, you should be able to:

• Set up and manage multiple named configurations

• Use configuration templates

• Describe OWB configurations in RAC environments

• Schedule ETL jobs


Lesson Agenda

• Set up and manage multiple named configurations– Explain the concept of multi-configuration – Relate locations, control centers, and named configurations– Describe how to apply multi-configuration to a Dev-QA-Prod

scenario– Use OWB configuration user interface to easily inspect and

manage multiple configurations





Enterprise ETL License Extends Core In-Database ETL

OWB In-Database• Integrated with Oracle Database 11g R2• Design ETL mappings• View HTML metadata reports• Perform data cleansing• Use GUI or scripting language

Data Profiling & Quality

ODI-EE license Application Adapters

Data Watch & Repair

Integrate with Oracle MDM:

• Siebel Universal Customer Master

• Product Information Management Data Hub

• Customer Data Hub

Create new metadata types Promote from

Dev>QA>PROD Navigate lineage & impact Propagate metadata changes Create advanced mappings

and process flows logic Create pluggable mappings Apply Slowly changing

dimensions type 2 and 3 Deploy XML file targets Use transportable modules Design in RAC environment

Access to data and metadata in:• SAP R/3• E-Business Suite• PeopleSoft• Siebel

• Profile tables, files, applications

• Detect or create data rules• Audit incoming data• Correct data

Oracle Warehouse Builder


Scenario Requiring Multiple Configurations

Problem: How do I configure and transition among development, QA, and production environments?

DevelopmentPhysical

implementation

QAPhysical

implementation

Production Physical

implementation

- No logging

- Nonparallel

- Tablespace: dev_data

- Table EMP Location: loc1

- No logging

- Parallel

- Tablespace: prod_data


Required development settings

Required production settings


Loose Coupling of Metadatawith Physical Implementations

OWB supports one logical model and multiple physical run times:

Configuration 1: Its control center points to the Development run-time location.

Configuration 2: Its control center points to the QA run-time location.

Configuration 3: Its control center points to the Production run-time location.

DevelopmentPhysical

implementation

QAPhysical

implementation

Production Physical

implementation


Each Configuration Records the Physical Settings of Its Target Environment

• Named configurations for multiple deployments

• No need to write scripts to change logging, tablespace names, and so on

Physicalconfiguration:

Development

- No logging

- Nonparallel

- Tablespace: dev_data


- No logging

- Parallel

- Tablespace: prod_data


Physicalconfiguration:

Production

Single logicaldesign


Multiple Named Configurations: Why and How

• Why should I use multiple named configurations?– To maintain a single design for objects– To change the generated code per target database– To deploy, without hard-coding and writing scripts, to

different repositories in a controlled way• How do I use multiple named configurations?

– Separate logical from physical with a loose coupling of logical design and physical implementation.

— Define named configurations (holding physical information for objects) for each of your run times.

— Active configuration substitutes physical properties into generated code.

– Deploy code into its targeted database.


Deploying a Selected Configuration

A single logical design can be deployed to different repositories by applying different configurations.

DevelopmentPhysical

implementation

QAPhysical

implementation

Production New software

release

Generate Deploy

CodeApply Devconfiguration.

Apply QAconfiguration.

Apply Prodconfiguration.

Singlerepository

Select an active

configuration.

Generate Deploy

Code

Generate Deploy

Code


Configurations, Control Centers, and Locations

Control center Locations1

nNamed

configuration1

1

Configurationpoints to one control center.

One “active”configuration

1 Control center can point to multiple source and target locations.

2

3


Creating Additional Configurations and Control Centers

4

1 2

3

Control center agents are required only in code template-based mappings, taught in a later lesson.


Setting the Active Configuration

• Only one configuration can be active at a time.

• There are two ways to set the active configuration.

To quickly check which configuration is active, examine the Design Center status bar.

1

2


Configuring Objects Across All Configurations

Highlightdifferences


Cloning a Database to Create Identical Dev-QA-Prod Systems

• In contrast to deploying different versions, if you want to rapidly roll out a set of identical systems, you should consider cloning the database.

• The process of cloning typically changes host names and service names.

• The host names and service names are stored in the control center repository in each target repository schema. You need to change their persisted values after cloning.

Clone and then change host and service names.

Designrepository

Host name: Asvce. Name: A

schema: A

Development

Host name: Xsvce. Name: X

schema: A

Production

Host name: Zsvce. Name: Z

schema: A

QA

Host name: Ysvce. Name: Y

schema: A


Practice 1-1 Overview: Using Multiple Named Configurations

This practice covers the following topics:

• Defining multiple configurations

• Comparing an object’s differing values across different configurations


Lesson Agenda






Configuration Templates

Configurationtemplate

Controlcenter

Configprops

Configprops

Configprops

Object

Object

Object

Physicalsystem

Location

Location

Logicalsystem

Module

Module

Associates Owns

Sets/overwrites

Owns

Imp

lemen

ted in


Creating a New Configuration Template

Configuration template has a column called “Seeded Default” that contains the default repository values.

The column to the right of the defaults contains the property values for a different configuration template.


Associating a Configuration Template with a Configuration

Create Configuration Wizard lets you select a different configuration template if you want to override the system’s default configuration values.

The Configurations drop-down list is now on the toolbar, and is therefore easily visible and accessible. Select Create New Configuration to create a new configuration.


Overriding Default Configuration Settings

If DEFAULT_CONFIGURATION is active, note that the CHANNELS table configuration shows default settings.

When PRD_CONFIG is active, the settings you applied for the PARALLEL property of the Tables object type is effective. So the CHANNELS table uses the new configuration settings.


Practice 1-2 Overview: Using Configuration Templates

In the hands-on practice, you will perform the following:

• Create a new configuration template

• Associate the new template with a new configuration


Lesson Agenda






Control CenterService

Control Center Service Failover on RAC

1. Control Center Service (CCS) node fails.

2. CCS goes down.

3. CCS comes up on a different node of the RAC.

4. CCS resumes activities.

Control center

Single logical

instance


Designrepository Control center

Control center

Single logical instance

RAC Deployment

Locations are defined using net service names, not host:port:service.


Supported and Unsupported RAC Features

• Load balancing– Connection load balancing based on server (supported)– Client-side load balancing (not supported)

• Failover types– Connect failover: node, listener, instance down (supported

with properly configured tnsnames.ora)– Transparent Application Failover (not supported)– Multiple concurrent Control Center Services (not supported)


Steps for Setting Up OWB in a RAC Environment

Install OWB.

Configure database and OWB.

Monitor nodes.

Troubleshoot.

1. Decide whether to use OWB with shared storage or with nonshared local disks on each RAC node. Same path for each OWB install.

2. Choose Cluster or Local Installation; run root.sh on each node.

4. Use Runtime Assistant on other nodes to register the repository.

3. Install OWB repository only once, to one node. If using a shared disk, install repository there.

6. Replicate RTREPOS.PROPERTIES and TNSNAMES.ORA on each node.

7. Define OWB locations with TNS names, not host:port:service.

8. Use OWB Browser to monitor, enable, or disable Control Center Service on a node.

9. Search logs on nodes, run helpful utilities, avoid common mistakes.

5. On the database, set MAX_COMMIT_PROPAGATION_DELAY to 0.


Lesson Agenda






Scheduling Concepts

Schedule_Module 1

EVERY_2_HOURS

MONTHLY_SALES

SALES_EVERY_30_MIN

Schedule_Module 2

HOURLY_LOAD


Creating a Schedule Module


Creating a Schedule


Create Schedule Wizard: Name and Description


Create Schedule Wizard: Start and End Time


Create Schedule Wizard: Frequency and Repeat Interval


Monthly Schedule

Monthly frequency

Repeat interval

Day of month


Editing a Schedule

Schedulepreview

Schedule runs at 9 AM, 11 AM, 1 PM, 3 PM, 5 PM

Specificationsfrom the wizard

Additionaladvancedspecificationsin the editor


Run One Week into the Next Quarter

Runquarterly

Run on the8th day aftereach quarter


Associating an Executable Object with a Schedule

Associate

executable

with a

schedule.

Deploy

SCHEDULE

- Start date and time

- Schedule frequency

- Repeat interval

- End date and time

EXECUTABLE OBJECT

- Mapping

- Transformation

- Process flow

Databasescheduler


Assigning a Schedule to an Executable Object

A scheduleassigned to theLOAD_SALESmapping

Sales_Quarter mapping configuration


Quiz

Which of the following statements are true?

a. OWB supports one logical model and multiple physical run times.

b. A single logical design can be deployed to different targets by applying different configurations.

c. Only one configuration can be active at a time.

d. The Create Configuration Wizard lets you select a different configuration template if you want to override the system’s default configuration values.


Summary

In this lesson, you should have learned how to:






Practice 1-3 Overview: Creating a Schedule

This practice covers the following topics:

• Using the scheduling wizard a schedule that activates every two hours

• Editing the schedule to define more advanced scheduling capabilities

• Attaching the schedule to a process flow

Documents

1 Copyright © 2009, Oracle. All rights reserved. Administrative Tasks in Warehouse Builder