Setting up the Oracle Warehouse Builder Project

Purpose

In this tutorial, you set up and configure the project environment for Oracle Warehouse Builder
11g Release 1.
You create a Warehouse Builder repository and log in to the Warehouse Builder Design Center.

Time to Complete

Approximately 40 minutes

Note: Instructions for downloading the OWB 11g SETUP scripts are provided later in this
tutorial.
This tutorial and its setup scripts support OWB 11g Release 1, only.
Earlier versions of this Oracle By Example tutorial are available for OWB 10g Releases 1 and 2.

Topics

This tutorial covers the following topics:

Overview
Prerequisites
If Using DB10gR2
Preparing the Database Instance
Setting up the Project Environment
Importing Source Metadata in Source Modules
Summary

Viewing Screenshots

Place the cursor over this icon to load and view all the screenshots for this tutorial.
(Caution: This action loads all screenshots simultaneously, so response time may be slow
depending on your Internet connection.

Note: Alternatively, you can place the cursor over each individual icon in the following steps to
load and view only the screenshot associated with that step.

Overview

In this tutorial, you learn how to set up and configure the Warehouse Builder environment.
You also use the Repository Assistant to create a user for logging in to the Oracle Warehouse
Builder repository database
where your warehouse design metadata is stored.
This tutorial is a pre-requisite to the following tutorials:

Examining Source Data using Data Profiling

Matching and Merging Records
Extracting, Transforming and Loading Data
Modeling the Target Schema
Using Experts to Automate Warehouse Builder Tasks

Back to Topic List

Prerequisites

Before starting this tutorial, you should:

1. Have Completed the installation of Oracle Database (Enterprise Edition) 10g Release 2 (patched
up to 10.2.0.3 for OLAP support) or 11g Release 1 (11.1.0.6).

Note: This hands-on tutorial has been tested using OWB 11g Release 1 on an Oracle Database
10g Release 2 (10.2.0.3) instance. You can choose to run the hands-on using Oracle Database
10g Release 2 (10.2.0.3) or 11g Release 1.

It is strongly recommended that you create a database named orcl for this course. Otherwise, you
need to substitute the Oracle Service Name of your database wherever you see orcl mentioned in
this course.

The SYSDBA username/password used throughout the course is sys/oracle. You may replace
the password with your SYS account password wherever required.

During the installation of the database, remember to include the sample schemas in the install
and also towards the end of the install, ensure you unlock the three sample schemas: OE, SH and
HR.

2. Have completed the installation of Oracle Warehouse Builder 11g Release 1. To simplify the
setup, this course assumes that the database and Warehouse Builder are on the same machine.
For this course, you are strongly encouraged to install the database and Warehouse Builder on
the same machine.

Note: If you are using Warehouse Builder 11g Release 1 with Database 10g Release 2, be sure to
install Warehouse Builder to an empty Oracle Home, not the Oracle Home of the database.

It is suggested that you set the Warehouse Builder home name to owb11gr1 and location to
something like c:\oracle\product\11.0\owb11gr1.
3. Note: The following is an optional prerequisite, and only required if you plan to work on Lesson
4, "Extracting, Transforming and Loading Data ":

Installed Oracle Workflow Server 2.6.4 as explained in the note below, and in step 4.

Note: If you are using an Oracle Database 10g Release 2 (10.2.0.3) instance with OWB 11g,
install Workflow Server 2.6.4 from the Warehouse Builder 11g installation's <OWB 11g
Home>\owb\wf\install directory, and invoke wfinstall.csh for Unix, or wfinstall.bat for Windows
platforms. You must install Workflow Server in your Oracle database home (not in OWB's home
or any other home).

If you are using an Oracle Database 11g instance with OWB 11g, you need to install a version of
Workflow Server 2.6.4 with changes for Database 11g. Go to the Database 11g installation's
<Oracle11g Database Home>\owb\wf\install directory, and invoke wfinstall.csh for Unix, or
wfinstall.bat for Windows platforms. You must install Workflow Server in your Oracle database
home (not in OWB's home or any other home).
4. To start the Workflow Server installation and configuration script on Windows:
In a command prompt window, change to the directory owb_home /owb/wf, and run
wfinstall.bat. For example:

C:\> cd owb_home \owb\wf\install

c:\cd owb_home /owb/wf\install> wfinstall.bat

To start the installation and configuration script on Linux:

In a Unix shell, change to the directory owb_home /owb/wf, and run wfinstall.csh. For example:

$ cd owb_home /owb/wf/install
$ wfinstall.csh

The Oracle Workflow Configuration Assistant dialog box appears.

Enter the following values:

For Install Option, choose Server Only

For Workflow Account, enter owf_mgr
For Workflow Password, enter your chosen password for the Workflow Account, such as
owf_mgr
For SYS Password, enter the SYS password for the database where you are installing
Oracle Workflow
For TNS Connect Descriptor, enter hostname : port : service_name, where the values of
hostname, port, and service_name correspond to your database
Note : Do not use a net service name as provided in your database tnsnames.ora file. The
Workflow Configuration Assistant does not reference your tnsnames.ora file in this
installation scenario.

When you have entered all necessary values, click Submit to start the Workflow configuration
process.
The configuration process will take several minutes.
You can check owb_home /owb/wf/install/wf.log for messages to follow the progress of the
 configuration process.

When the process is complete, the Workflow Configuration Assistant displays a dialog box with
the message "Workflow Configuration has completed successfully". Click OK . The installation
script now exits.

Finally, you need to grant the "EXECUTE ANY PROCEDURE" privilege to the owf_mgr user.
Connect to SQL Plus as "SYS as sysdba", and issue the command: grant execute any procedure
to owf_mgr

5. Have downloaded the owbdemo_files.zip file by right-clicking here and selecting Save Target
As from the pop-up menu. Direct the download to c:\ root directory on your computer's hard
drive.

Extract the files from the zip file to the c:\ root path.

Back to Topic List

If Using DB10gR2
Note: If you are using Oracle Database 10gR2 instead of Database 11g with this tutorial, you
must perform the following steps
to create the OWBSYS user and enable access to the Control Center and workspaces .
If you are using Database 11g, skip ahead to the subtopic "Preparing the Database Instance ".

1. If using DB 10gR2, you need to run a SQL script to create the OWBSYS repository schema that
automatically comes with the install of DB11g, and which is needed by OWB 11g.

This script, <your OWB home>/OWB/UnifiedRepos/cat_owb.sql, installs the OWBSYS database

user that is otherwise automatically created when installing DB 11g.

Note: The method by which you invoke SQL Plus is important. Do not invoke SQL Plus from
Start > Programs > Oracle database home folder or Warehouse Builder folder! Instead, invoke
SQL Plus from Start > Run > cmd.exe. Type the Path command and press Enter. You want to
check that Warehouse Builder is near the front of the path statement, so that the SQL Plus session
will invoke from the Warehouse Builder installation. If not, you may need to temporarily set the
path, such as Path=<Warehouse Builder home>\bin. Then invoke SQL Plus as SYS with
SYSDBA privileges. For example, at the command line you might type: sqlplus sys/<sys
password> as sysdba.

Connect to SQL Plus as sysdba and issue the following command to create OWBSYS:

@<your OWB home>/owb/UnifiedRepos/cat_owb.sql;

Press Enter. You will be prompted for a tablespace for the OWBSYS user. For this training, it is
recommended that you specify the USERS tablespace. Type users and press Enter.
 When this command finishes successfully, you will be prompted "If you are NOT using an OWB
installed in the Oracle database home, please now run reset_owbcc_home".

2. Earlier, you were instructed to install Warehouse Builder in an Oracle home other than the
database Oracle home. To ensure access to the Control Center on the 10g R2 database, run the
script UnifiedRepos/reset_owbcc_home.sql and pass in your Oracle home for Warehouse Builder.
Run the script as a system privileged user such as SYS or SYSTEM. For example, type the
following command at the command prompt:

SQL> @c:\oracle\OWB_home_11g\owb\UnifiedRepos\reset_owbcc_home;

Press Enter. You will be prompted for the full path of the Oracle home for the OWB Control
Center install. First read the following note.

Note: In the following example, observe the required use of forward slashes "/", even when using
a Windows machine. Also please note that your response with the full path must be case-
sensitive! Be sure to type the drive letter in uppercase, such as "C:". And follow the case
sensitivity of the folder names in the path of the Oracle home for OWB. Your response should
appear somewhat like the following example:

C:/oracle/OWB_home_11g

Press Enter.

3. If the strong password option is enabled on the Database, then after creating OWBSYS, you need
to unlock the OWBSYS account and unexpire its password. Proceed with the 2nd and 3rd SQL
Plus commands to unlock the OWBSYS account and assign a password also named OWBSYS:

alter user OWBSYS account unlock;

alter user OWBSYS identified by OWBSYS;

The requirements explained above are also mentioned in the OWB 11g Installation Guide
documentation, in the section titled Hosting the Repository on Oracle Database 10g Release 2.

4. For each Warehouse Builder client installation, enable access to the workspaces hosted on your
10gR2 database.

By default, Warehouse Builder 11g Release 1 (11.1) clients are set to connect to workspaces
hosted on an Oracle 11g Database. That is, the Warehouse Builder repository is assumed to be
hosted on an Oracle 11g Database.

To enable access to a 10gR2 repository and its workspaces, alter the file < owb home>
 /owb/bin/admin/Preference.properties on your machine. If the file does not exist, you can create
it based on the example file available in the same directory, Preference.properties.tmp.

In the preference properties file, add a property REPOS_DB_VERSION_ALLOWED and set its
value to: Oracle 10g, Oracle 11g. (This property may already be present.)

Back to Topic List

Preparing the Database Instance

To prepare your database instance for this OBE tutorial, you need to perform the following steps:

Run the SQL Scripts

Import the dq_src.dmp File

Back to Topic List

Run the SQL Scripts

Before you can begin working with the tutorials, you need to run the create_user.sql script and
unlock.sql script from the owbdemo_files.zip file that you downloaded.

To run the SQL scripts, perform the following steps:

1. The create_user.sql script creates a DQ_SRC user and grants connect, resource, and create any
view privileges to the user. In the next topic, you import data through a dq_src.dmp file into this
dq_src schema/user.

Log in to SQL*Plus as sys and run the create_user.sql script that you downloaded into the
c:\owbdemo_files folder.

To run the script, enter the following command at the SQL> prompt:

@c:\owbdemo_files\create_user.sql
2 In case you did not unlock the sample schema accounts as mentioned in the prerequisite 1 in this
tutorial, run the unlock.sql script to ensure that all the required accounts are unlocked. This script
also unlocks the Oracle Workflow user account, owf_mgr.

If you did not install and configure Oracle Workflow, edit the unlock.sql script and remove the
alter command for owf_mgr before running the script.

Assuming you are still logged in as sys, to run the unlock.sql script, enter the following
command at the SQL> prompt:

@c:\owbdemo_files\unlock.sql
 Enter quit at the SQL> prompt to exit SQL Plus.

Back to Topic

Import the dq_src.dmp File

To import the dq_src.dmp file, perform the following steps:

1. To import the dmp file, invoke Start > Run and execute cmd to open a command line window.
Enter the following command:

<ORACLE_DATABASE_HOME>\bin\imp dq_src/dq_src@<ORCL or your

database service name> file=<PATH>\dq_src.dmp full=y

Substitute <ORACLE_DATABASE_HOME> with your Oracle Database home location and

<PATH> with the location where you extracted the dq_src.dmp file. Also, ensure you enter the
 correct database service name.

When the import finishes, exit out of the command line window.

Back to Topic

Back to Topic List

Setting Up the Project Environment

To setup and configure the Oracle Warehouse Builder project environment, you need to perform
the following steps:
Create a Repository Using the Repository Assistant
Import the Start.mdl File
Create Target Users
Register the Oracle Workflow User
Set Security Preferences
Connect the Modules with the Target Schema Locations

Back to Topic List

Create a Repository Using the Repository Assistant

When logging in to the OWB Design Center for the first time, you can create a Warehouse
Builder user with which to log in.
You create a new workspace, a new workspace user, and install the Warehouse Builder
repository.

1. Select Start > Programs > {your Oracle - OWB11gR1clientHome} > Warehouse Builder >
Administration > Repository Assistant. The Welcome screen of the Repository Assistant
Wizard appears. Click Next.

2. In the Database Information window, enter localhost or <your machine name > as the host
name, 1521 as the port number, and orcl as the Oracle service name or <the database service
name you are using>. Click Next.

3. In the Choose Operation window, select the Manage Warehouse Builder workspaces option.
 Click Next.

4. In the Choose Workspace Operations window, select Create a new Warehouse Builder
workspace. Click Next.
5. In the New or Existing User window, click Create a workspace with a new user as workspace
owner. Click Next.
6. In the DBA Information window, enter system as the user name, and oracle <or whatever is
your database system password> as the password. Click Next.
7. In the Workspace Owner (New) window, enter owb/owb as the workspace owner
username/password. Confirm the password as owb. Enter my_workspace as the workspace
name. Click Next.
8. In the OWBSYS Information window, enter owbsys/owbsys as the user name and password .
Click Next.
9. In the Select Tablespaces window, you can specify the tablespaces you are using for data,
indexes, temporary data, and snapshots. For this course, you use the default tablespaces. Click
Next.
10. In the Select Languages window, accept the default. Click Next.
11. In the Workspace Users (Optional) window, you can create a workspace user or select an
existing database user and register it as a Warehouse Builder user. This user has privileges to
work in the design center as well as be able to deploy and execute objects through the Control
Center. This user can also be a target schema. For now, because you don't intend to use a
workspace user, click Next to move to the next window.
In the Summary window, verify the details and click Finish. An Installation Progress window
displays. The installation of the repository owner takes several minutes.

An Installation Successful window displays. Click OK. The Repository Assistant closes.
 Back to Topic

Import the Start.mdl File

You can use the Warehouse Builder Design Center to import metadata. To import objects from
the start.mdl file, perform the following steps:

1. First, you need to log in to the Design Center. Select Start > Programs > {your Oracle - OWB
clientHome} > Warehouse Builder > Design Center.

The Design Center Logon window displays. Enter owb as username and password. If not
showing the connection details, click Show Details.

Select the Connection details option, if not selected already, and specify the connection details.

Enter host as localhost, port as 1521, and service name as orcl or <your database service name>.
Click OK.

2. The Design Center displays.

Note: The Design Center is the main client application of Warehouse Builder. It provides easy-
to-use graphical interfaces that enables you to design, deploy, create, and monitor business
intelligence systems.
 The Design Center is divided into three panels: Project Explorer, Connection Explorer, and
Global Explorer, as shown in the screenshot below. The Project Explorer on the left contains one
project: MY_PROJECT, an empty project created when Warehouse Builder is installed.

3. To start the import mdl process, from the Design menu, select Import > Warehouse Builder
Metadata.
 The Metadata Import window displays.

Note: If you had made changes to the repository metadata before running the import utility, the
Warehouse Builder Warning dialog is displayed. Click Save to save changes or Rollback to
revert to the previously saved version. If you have not made any changes to the repository
metadata after last saving the design, Warehouse Builder displays the Metadata Import dialog.

4. In the Metadata Import window, click Browse to specify the filename for the metadata file. In
the Open dialog box, select the start.mdl file from c:\owbdemo_files\ or from the location you
saved the file. Note or modify the path of the log file in case you need to review the log later. If
you attempt multiple imports from the same MDL file, and do not specify a new path for the log
file, you will receive a pop-up reminder asking if you wish to overwrite the existing log file.

Note: Whenever you export or import repository metadata, the MDL writes diagnostic and
statistical information to a log file. You can specify the location of the log file when you invoke
MDL using the Metadata Loader utility. The log file enables you to monitor and troubleshoot
export and import activities in detail. The import log file contains information about the object
 types imported, and displays the total number of objects added, replaced, skipped, or deleted.

Accept the default for the Object Selection, Import Option, and Match By options. Click Import.

5. After the import is completed, click Show Details. It shows the message log of the metadata
imported. Scroll in the window to verify that there is no error reported.
 Click Close.

6. The migrated project HANDSON is added in the Project Explorer panel. Expand Handson >
Databases > Oracle and examine the two imported modules, DQ_TGT and DP_TGT.
 From Design menu, select Save All and click Yes in the Warehouse Builder warning dialog box
to commit the changes.

Back to Topic

Create Target Users

You noticed the two modules, DQ_TGT and DP_TGT inside the HANDSON project that you
imported. Every target module must be mapped to a target user schema. This target schema
physically stores your target objects on deployment. Also, each target module references a target
schema by an assigned location.

To create DQ_TGT and DP_TGT target schema users, perform the following steps:

1. In the Global Explorer panel, expand the Security node. Right-click the Users node and select
New.
 Note: You must save or revert your changes before creating a new user. To save previous
changes, select Save All from the Design menu.

2. On the Create User page, you can select from the available list of database users or create a new
one.

Click on Create DB User to create a new target user in the database.

3. To be able to create a new target user, you need to have DBA privileges. In the Create Database
User dialog box, enter system as DBA name and oracle or <your system account password> as
the DBA password.

Enter DQ_TGT/DQ_TGT as the username/password for the new DB user. Accept the defaults
for the tablespace properties. Click OK.
4. To create another target schema user, DP_TGT, on the Create User page, click Create DB User
again.

In the Create Database User dialog box, enter system as DBA name and oracle or <your system
account password> as the DBA password.

Enter DP_TGT/DP_TGT as the username/password for the new DB user. Accept the defaults
for the tablespace properties.
Click OK. Observe both DQ_TGT and DP_TGT have been added to the Selected Users list.
 Click OK. The Register Users Progress window shows the task progress. When the progress
window closes, examine the Users node. You find the users DQ_TGT and DP_TGT added to the
list of existing target users.

5. You now create the target locations for the DQ_TGT and DP_TGT users.

Note: Locations define information about the database schema or target tool where you will be
deploying objects. Locations are specific to a type of module, such as Oracle Database, SAP, or
flat file.

Expand Locations > Databases. Right-click Oracle and select New.

In the Create Oracle Database Location window, specify the following information:

In the Name field, change ORACLE_LOCATION1 to DQ_TGT_LOCATION

User Name: DQ_TGT
Password: DQ_TGT
Host: localhost or machine name
Port: 1521
Service Name: orcl
Schema: DQ_TGT
Version: 10.2 or 11.1, depending on database version you are using

Click Test Connection. A success message should appear.

 Click OK. Now repeat the above steps to create the location for DP_TGT.
In the Create Oracle Database Location window, specify the following information:

In the Name field, change ORACLE_LOCATION1 to DP_TGT_LOCATION

User Name: DP_TGT
Password: DP_TGT
Host: localhost or machine name
Port: 1521
Service Name: orcl
Schema: DP_TGT
Version: 10.2 or 11.1, depending on database version you are using

Click Test Connection. A success message should appear. Click OK.

6. Examine the Oracle Locations node and note that new locations, DQ_TGT_LOCATION and
DP_TGT_LOCATION have been added.
 Note: Locations define information about the database schema or target tool where you deploy
objects. Locations are specific to a type of module, such as Oracle Database, SAP, or flat file.

From Design menu, select Save All. In Warehouse Builder warning dialog box , click Yes to
commit the changes.

Back to Topic

Register the Oracle Workflow User

Note: This is an optional step and only required if you installed and configured Oracle
Workflow with an intention to complete "Extracting, Transforming and Loading Data"
tutorial.

You need to grant specific roles to the Oracle Workflow(OWF) user, owf_mgr, for it to have the
privileges to execute a process flow in the Control Center.

You do not have to embed the password for the Control Center in database-links owned by the
OWF user. The Control Center user is highly privileged and its password is tightly controlled.
To register the OWF user, you use the Register Warehouse Builder Users wizard from the
Security > Users node in Global Explorer panel. To get access to the security node, ensure you
log in to the design center as the repository owner.

To register the owf_mgr user, perform the following steps:

1. In the Global Explorer panel, expand the Security node. Right-click the Users node and select
New.

Note: You must save or revert your changes before creating a new user. To save previous
changes, select Save All from the Design menu.

The Create User dialog is launched.

2. On the Create User dialog, you can select from the available list of database users or create a
new one that will be automatically registered as a Warehouse Builder user.

Select owf_mgr from the Available DB Users list and click > to move it to Selected Users list.
 Click OK.

3. Notice that owf_mgr user is added to the Security > Users node in the Global Explorer panel.

From Design menu, select Save All. In Warehouse Builder warning dialog box , click Yes to
save the changes.
 Back to Topic

Set Security Preferences

To set security preferences, perform the following steps:

1. From the Tools menu, select Preferences.

2. In the Preferences window, select Security Parameters. In the right panel, check Persist
location password in metadata. Also, check Share location password during run time, as
shown in the screenshot.
 Click OK. From Design menu, select Save All. In Warehouse Builder warning dialog box , click
Yes to save the changes.

Back to Topic

Connect the Modules with the Target Schema Locations

When you imported the start.mdl, you had the DQ_TGT and DP_TGT modules already created
for you and then you followed steps to create two target users, DQ_TGT and DP_TGT
referenced by two locations, DQ_TGT_LOCATION and DP_TGT_LOCATION respectively.
Now, you need to link the target modules with each of their respective locations, so that
whatever you design in a module, on deployment those objects physically exist on the target
schema the location points to.
To connect the modules with the locations, perform the following steps:

1. First, you test your locations to verify the connection. In the Connection Explorer panel, expand
Locations > Databases > Oracle. Double-click DP_TGT_LOCATION.

In the Edit Oracle Database Location window, enter DP_TGT in the Password field. Note, the
Host field should be set to localhost. If the Host field is set to your machine name, enter
localhost. Verify other connection details and click Test Connection.

If connection is successful, click OK. If the connection is not successful, check the connection
details and try again.

Similarly, test DQ_TGT_LOCATION. In the Edit Database Location window, enter DQ_TGT
in the Password field. Again, verify the Host field. Note, the Host field should be set to
 localhost. If the Host field is set to your machine name, enter localhost. Click Test Connection.

If connection is successful, click OK. If the connection is not successful, check the connection
details and try again.

2. In the Project Explorer panel, expand Databases > Oracle. Double-click DP_TGT. In the Edit
Module window, select Metadata Location tab. From the Location drop down list, select
DP_TGT_LOCATION.
Now, select the Data Locations tab. Select DP_TGT_LOCATION from the Available
locations list and click > to move it to the Selected Locations list.
 Click OK.

3. Similarly, you connect the DQ_TGT module with DQ_TGT_LOCATION. Double-click

DQ_TGT. In the Edit Module window, select Metadata Location tab. From the Location drop
down list, select DQ_TGT_LOCATION.
Now, select the Data Locations tab. Select DQ_TGT_LOCATION from the Available
locations list and click > to move it to the Selected Locations list.
 Click OK.

4. You also need to configure the module to pick the correct data location. Right-click DP_TGT
and select Configure.
In Configuration Properties window, for Location property, select
DP_TGT_LOCATION(Default) and click OK.
5. Similarly, right-click DQ_TGT and select Configure. In Configuration Properties window, for
Location property, select DQ_TGT_LOCATION(Default).
 Click OK.

From Design menu, select Save All. In Warehouse Builder warning dialog box , click Yes to
save the changes.

Back to Topic

Back to Topic List

Importing Source Metadata in Source Modules

In Warehouse Builder, you create modules for various sources, such as for Oracle-based
relational table source metadata. In the subsequent tutorials that you may take up to perform the
hands-on, you may need to create source modules pointing to a Oracle database sample schema
such as OE or the DQ_SRC schema where-in you imported the dq_src.dmp file in the previous
topic.

Note: Depending on the tutorial, you plan to work through, follow the topics below to
create the relevant source module. When you create a source module, you also import the
required metadata using the Import Metadata Wizard.

If you plan to work on Examining Source Data Using Data Profiling and/or Matching and
Merging Records tutorial, perform "Importing Metadata in DQ_SRC Module" topic. If you
plan to work on Extracting, Transforming and Loading Data and/or Using Experts to
Automate Warehouse Builder Tasks tutorial, perform "Importing Metadata in OE Module"
topic. Obviously, if you want to work through all the four tutorials, you need to complete both
topics, mentioned below:

Importing Metadata in DQ_SRC Module

Importing Metadata in OE Module

Back to Topic List

Importing Metadata in DQ_SRC Module

To import metadata in DQ_SRC module, perform the following steps:

1. First you need to create the DQ_SRC module, before you can import metadata into it.

Assuming that you logged in as owb user, in the Project Explorer panel, select the HANDSON
project, expand Databases. Right-click Oracle and select New.

The Create Module wizard launches. Click Next to skip the Welcome page.
2. In the Name and Description page, enter DQ_SRC as the name of the module. Accept
Development as the module status and select Data Source as the module type.

Click Next.

3. In Connection Information page, you specify the location specifications of the source data.
Observe that Warehouse Builder gives a default name, DQ_SRC_LOCATION1, to the
location. Click Edit to specify the details.
4. The Edit Oracle Database Location dialog appears. Provide the following information to create a
fully qualified location:

Name: DQ_SRC_LOCATION (remove the 1 from the default

name)
User Name: DQ_SRC
Password: DQ_SRC
Host Name: localhost
Port Number: 1521
Service Name: orcl
Schema: DQ_SRC
Version: 10.2 <or 11.1, depending on your source database
version>

Click Test Connection to test the connection.

If the connection is not successful, check the connection details. Otherwise, click OK.

Ensure that the "Import after finish" option is checked. Click Next.
 In the summary page, examine the details and click Finish. The Import Metadata Wizard
launches. Click Next on the Welcome page.

5. In the Filter Information page, you select the object types you want to import. Uncheck all
boxes, except Table and View and click Next.
6. In the Object Selection page, hold shift and select Tables and Views, and click > to move all the
tables to the Selected Objects list.
 Click Next.

7. In Summary and Import page, examine the import details. Eleven objects should be listed, the
order of which is not important. Click Finish.
 The Import Progress dialog shows the import progress. Click OK on the Import Results window.
From Design menu, select Save All. In Warehouse Builder warning dialog box , click Yes to
save your work.

Back to Topic

Importing Metadata in OE Module

To import metadata in OE module, perform the following steps:

1. First you create the OE module, before you can import metadata into it.

Assuming that you logged in as OWB user, in the Project Explorer panel, select the HANDSON
project, expand Databases node. Right-click Oracle and select New.
 The Create Module wizard launches. Click Next to skip the Welcome page.

2. In the Name and Description page, enter OE as the name of the module. Accept Development as
the module status and select Data Source as the module type.
 Click Next.

3. In Connection Information page, you specify the location specifications of the source data.
Observe that Warehouse Builder gives a default name,OE_LOCATION1, to the location. Click
Edit to specify the details.
4. The Edit Oracle Database Location dialog appears. Provide the following information to create a
fully qualified location:

Name: OE_LOCATION (remove the 1 from the default name)

User Name: OE
Password: OE
Host Name: localhost
Port Number: 1521
Service Name: orcl
Schema: OE
Version: 10.2

Click Test Connection to test the connection.

If the connection is not successful, check the connection details. Otherwise, click OK.

Ensure that the "Import after finish" option is checked. Click Next.
 In the summary page, examine the details and click Finish. The Import Metadata Wizard
launches. Click Next on the Welcome page.

5. In the Filter Information page, you select the object types you want to import. Accept the default
selection. Click Next.
6. In the Object Selection page, select Tables and click > to move all the tables to the Selected
Objects list.
 Click Next.

7. In Summary and Import page, examine the import details and click Finish.
 The Import Progress dialog shows the import progress. Click OK on the Import Results window.
From Design menu, select Save All .In Warehouse Builder warning dialog box , click Yes to
save the changes.

Back to Topic

Back to Topic List

Summary

In this tutorial, you learned how to:

Prepare your Database Instance for subsequent tutorials

Setup the Warehouse Builder Project Environment for the
subsequent tutorials
Import Source Metadata in Source Modules
 Back to Topic List

Place the cursor over this icon to hide all screenshots.