Installing and Setting Up the Warehouse Builder Environment

Installing and Setting Up the Warehouse Builder Environment

Data Integration and ETL with Oracle Warehouse Builder: Part 1 1 - 2
Objectives After completing this lesson, you should be able to do the following: Describe Oracle Warehouse Builder (OWB) Explain OWB In-Database and identify other licenses Identify a variety of possible installation configurations Identify the supported sources and targets Create the workspace and the workspace users Objectives This lesson provides an introduction to Oracle Warehouse Builder and its various components. You learn about Warehouse Builder's various packaging and licensing options and also identify the supported sources and targets. You also learn how to create a workspace, a workspace owner, and a workspace user. Data Integration and ETL with Oracle Warehouse Builder: Part

Lesson Agenda Oracle Warehouse Builder: Introduction Oracle Warehouse Builder Installation: OWBSYS schema Server and stand-alone installation Installing on Database 10g R2 or 11g R1 Workspace, Workspace Owners, and Users Using the Repository Assistant Supported operating systems (OS), sources, targets, and optional components Classroom configuration and documentation resources Data Integration and ETL with Oracle Warehouse Builder: Part

What Is Oracle Warehouse Builder?
Oracle Warehouse Builder (OWB) is a comprehensive data integration, data warehousing, data quality, and metadata management solution designed for the Oracle database. OWB is an integral part of Oracle Database and is installed as part of every database installation (except Oracle Database XE) What Is Oracle Warehouse Builder? Oracle Warehouse Builder 11g Release 2 (referred to throughout this course as OWB 11.2 or generically as Warehouse Builder) is a comprehensive data integration, data warehousing, data quality, and metadata management solution designed for the Oracle database. OWB is completely integrated with the installation of the Oracle database since the 11g Release 1 version. You can use Warehouse Builder to: Model data and perform extraction, transformation, and loading (ETL) Manage the full life cycle of data and metadata Maintain data quality using data profiling and cleansing Integrate with OBI EE for reporting Data Integration and ETL with Oracle Warehouse Builder: Part

Producing Quality Information
Business intelligence Transformation Action Data Information Knowledge (quality information) Warehouse Builder enables the extraction, transformation, and loading of data to produce quality information in the Oracle database. Producing Quality Information Gathered information 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 complete solution that you can use to create quality information. 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 quality information, Warehouse Builder integrates with business intelligence enterprise tools, so that you can easily create reports that transform this information into knowledge. The organization 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 Data Integration and ETL with Oracle Warehouse Builder: Part

Managing the Full Life Cycle of Metadata and Data
OWB provides data quality, data auditing, fully integrated relational and dimensional modeling, and full life-cycle management of data and metadata. OWB supports data integration and management activities including: Providing extraction, transformation, and loading (ETL) Consolidating data from disparate data sources Migrating data from legacy systems Data modeling of relational and dimensional structures Designing and managing corporate metadata Cleaning data to provide quality information Profiling and auditing data quality Data Integration and ETL with Oracle Warehouse Builder: Part

Basic Process Flow of Design and Deployment
Design target object metadata. 1 OWB client Map source to target with transformations. 3 2 Validate, generate, and deploy the code. 4 Extract source metadata: Relational databases (Oracle, Non-Oracle) Flat files Mainframe (COBOL Copybooks) Applications XML Derive and deploy BI reporting infrastructure. 5 OWB Workspace Sources Target warehouse and data marts 6 Basic Process Flow of Design and Deployment The 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. In OWB 11.2, for heterogeneous sources, you can design code template mappings discussed later in Part 2 of the course. 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 OBI SE or OBI EE. Integration with reporting tools enables easier development of business intelligence information systems. OWB 11.2 integrates with both Oracle Business Intelligence Enterprise Edition and Standard Edition. You can use Warehouse Builder to derive and manage the BI metadata and then use OBI EE tools to build reports on the existing data warehouse. Extract, transform, and load data. Data Integration and ETL with Oracle Warehouse Builder: Part

Basic Process Flow of Design and Deployment
Design target object metadata. 1 OWB client Map source to target with transformations. 3 2 Validate, generate, and deploy the code. 4 Extract source metadata: Relational databases (Oracle, Non-Oracle) Flat files Mainframe (COBOL Copybooks) Applications XML Derive and deploy BI reporting infrastructure. 5 OWB Workspace Sources Target warehouse and data marts 6 Basic Process Flow of Design and Deployment (continued) 6. Extract, transform, and load data. Execute the mapping scripts to extract source data and load it into the warehouse or data mart. Extract, transform, and load data. Data Integration and ETL with Oracle Warehouse Builder: Part

Oracle Warehouse Builder Licensing
OWB In-Database Integrated with Oracle Database Design ETL mappings View HTML Metadata reports Perform basic data cleansing Use GUI or scripting language Part 1 course ODI-EE license Application Adapters Data Profiling & Quality Data Watch & Repair Part 2 course Licensing is subject to change. For latest information, see Oracle Warehouse Builder Licensing This information regarding licensing is here merely to put into context the content covered in this course. Licensing is subject to change. Complete and official licensing information is available from the OWB home page at OWB In-Database OWB In-Database refers to the subset of OWB functionality included in the Oracle Database license and also preinstalled and embedded in the Oracle Database product. It is the focus of this course. It is the core offering of Warehouse Builder functionality integrated with the Oracle Database 11g Release 2 that enables you to build a basic Oracle data warehouse. The aim of the OWB In-Database functionality is to provide core bulk ETL functionality as part of the Oracle Database 11g Standard editions (SE, SE1), Enterprise edition (EE), and the DB Machine. It is not part of Oracle Express (XE) edition. This functionality includes the graphical user interface for designing and running ETL mappings and simple process flows. It also includes OMB*Plus, a complete scripting language and basic data cleansing functionality for name and address cleansing and fuzzy matching and merging of data. Note: Part 1 of this course covers the features of the OWB In-Database. Part 2 of this course focuses on the features and functionality that are included in the ODI-EE license. There is only one exception, the relational modeling feature, which is included in OWB In-Database but covered extensively in Part 2 of this course. Data Integration and ETL with Oracle Warehouse Builder: Part

Oracle Warehouse Builder Licensing Oracle Warehouse Builder
OWB In-Database Integrated with Oracle Database Design ETL mappings View HTML Metadata reports Perform basic data cleansing Use GUI or scripting language ODI-EE license Open connectivity using code templates SOA Integration Create new metadata types Multi Configuration Navigate lineage & impact Create advanced mappings and process flows Create pluggable mappings Apply Slowly changing dimensions type 2, 3 Deploy XML file targets Use Transportable modules Design in RAC environment Access to data and metadata in: SAP R/3 eBusiness Suite Peoplesoft Siebel Application Adapters Data Profiling & Quality Profile tables, files, applications Detect or create data rules Audit incoming data Correct data Data Watch & Repair Data quality solution for Oracle MDM: Siebel Universal Customer Master Product Information Management Data Hub Customer Data Hub Oracle Warehouse Builder Licensing (continued) ODI-EE License: Oracle Data Integration Enterprise Edition (ODI-EE) is a license that entitles customers to implement both ODI and OWB. The focus of Part 2 of this course is the functionality available in the ODI-EE license. The two main features included in this license are: Expanded heterogeneous source support Full support for service-oriented architecture for data integration It is now really flexible to access different types of sources. It is quite simple to add a new platform to extract data from. The actual code generated then uses the so-called code templates, which are templates with custom code. The SOA integration is briefly described later in this lesson. This license is also available for advanced ETL needs such as interactive lineage and impact analysis, extensible metadata, working in an Oracle RAC environment, and implementing slowly changing dimensions types 2 and 3. The aim of this license is to support large-scale and complex deployments by improving the scalability and performance of ETL jobs. It also has functionality to effectively manage multiple-environment deployments that are typical of enterprise data warehouse projects. This license also provides support for pluggable mappings and user-defined objects that can be crucial for enhancing a developer’s productivity. Licensing is subject to change. For latest information, see Data Integration and ETL with Oracle Warehouse Builder: Part

Oracle Warehouse Builder Licensing Oracle Warehouse Builder
Oracle Warehouse Builder Licensing (continued) Data Profiling and Quality: Is licensed as a separate option to the Oracle Database. This option enables you to profile any data that OWB can connect to without the need to stage the data. That is, OWB can profile files, tables, and ERP systems such as SAP R/3 without moving the data first. This option contains the following functionalities: Discovering data anomalies Identifying and creating data rules Autocorrecting data anomalies Auditing ETL jobs (and taking action if data quality is too low) Data Watch and Repair: Is an option that provides specific data rules for ensuring data quality with Oracle Master Data Management. This requires both the Oracle Database Enterprise Edition and the Warehouse Builder Data Profiling and Quality option. Application Adapters: Enable customers to quickly and easily extract data from (and in some cases target data to) their customer relationship management (CRM) and enterprise resource planning (ERP) applications. It enables access to data and metadata in: SAP R/3 E-Business Suite PeopleSoft Siebel Oracle Warehouse Builder Licensing Oracle Warehouse Builder OWB In-Database Integrated with Oracle Database 11.2 Design ETL mappings View HTML Metadata reports Perform basic data cleansing Use GUI or scripting language ODI-EE license 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, 3 Deploy XML file targets Use Transportable modules Design in RAC environment Access to data and metadata in: SAP R/3 eBusiness Suite Peoplesoft Siebel Application Adapters Data Profiling & Quality Profile tables, files, applications Detect or create data rules Audit incoming data Correct data Data Watch & Repair Data quality solution for Oracle MDM: Siebel Universal Customer Master Product Information Management Data Hub Customer Data Hub Licensing is subject to change. For latest information, see Data Integration and ETL with Oracle Warehouse Builder: Part

Connectivity Options Is integrated with Oracle Database Provides rich file support for reading and writing Can connect transparently using Database Gateways Can connect applications using the Application adapters for: Oracle E-Business Suite Peoplesoft Siebel SAP Can connect to Oracle Master Data Management through Data Watch and Repair for MDM Adapter Provides open connectivity using open Code Template Framework Connectivity Options Oracle Database 11g is supported as both an OWB source and a target. The support is closely linked to the simplified installation of OWB 11g as part of the Database 11g installation. The ability of OWB to connect transparently to non-Oracle systems continues with OWB 11g support for Gateway 11g. A connectivity feature introduced in OWB 11g R1 is the optional Siebel Adapter. Another connectivity feature was introduced in OWB 11g R1 via the Database 11g Patch This feature is the optional Data Watch and Repair for MDM Adapter. OWB 11.2 introduces open connectivity options that enable native access using Code Templates. The Code Template Framework is based on Oracle Data Integrator’s (ODI) Knowledge Module technology. This is available in the ODI-EE license and is covered in Part 2 of the course. The connectivity options are described below: ODBC/Gateways: leverage the Oracle Database Gateways. SQLLoader and External table: Rich file support for reading and writing files, both for the metadata captured about the file and the options exposed for processing efficiently Connectors: are the Application Connectors for SAP, EBS, Peoplesoft, Siebel and so on. Change Data Capture (CDC)/JDBC/Native loaders: CDC is for near real-time mappings and CDC code templates. JDBC and native loaders are used by the code templates. Data Integration and ETL with Oracle Warehouse Builder: Part

BI Environment from an OWB Perspective
Oracle Warehouse Builder Data sources Oracle BI OBI EE Server Data Siebel CRM Data Data Warehouse OBI EE Enterprise Semantic Layer (RPD) Oracle EBS Dashboards ETL Data objects Data quality Other sources Distribute metadata SAP/R3 OBI SE End-user layer Ad hoc reports Database Repository Metadata Data BI Environment from an OWB Perspective Warehouse Builder integrates with the Oracle Business Intelligence Enterprise Edition (OBI EE) tool. Using OWB, you can deploy derived metadata from the Warehouse Builder repository to OBI EE. In OWB 10g Release 2, the first version of this feature integrated Oracle BI Standard Edition (originally known as Oracle Discoverer). It continues to integrate OBI SE as it used to. In OWB, the repository is the center for metadata. Consolidating all metadata in a single place allows Warehouse Builder to deliver attribute-level lineage and impact analysis from the source to various query tools. You can use Warehouse Builder to derive and manage the BI metadata and then use OBI EE tools to build reports (ad hoc or dashboards) on the existing data warehouse. It also becomes easier to determine the impact of the changes all the way from the source to the end-user targets because there is a single metadata source. PeopleSoft Data Integration and ETL with Oracle Warehouse Builder: Part

Full Support for SOA Warehouse Builder fully supports service-oriented architectures for data integration. OWB 11.2 can be used to: Publish a Web service Consume an existing Web service The new Application Server module is introduced to support Web services. Two types of Application Server modules: Public and Private For more information, refer to the "Appendix C: Service-Oriented Architectures" in Part 2 of the course. Full Support for SOA There is an emerging need to deliver more and more infrastructure capabilities in the form of services. In a Service-Oriented Architecture (SOA), the Web services approach allows disparate technologies to be integrated in an easy and simple way through the use of standards. Web services are application components that use open, XML-based standards and transport protocols to exchange data with calling clients. Data integration services, including data quality and metadata services, are suited for this architecture so that any application enabled for these SOA applications can use the Warehouse Builder infrastructure. OWB 11.2 has been extended to enable creating and managing Web services easily. OWB 11.2 can be used to: Publish a Web service Consume or use an existing Web service Examples: Run a mapping or process flow as a Web service Run a Code Template–based mapping as a Web service In OWB 11.2, a new module, the Application Server module, is introduced to support Web services. There are two types of Application Server modules: Public and Private. Data Integration and ETL with Oracle Warehouse Builder: Part

Installing Oracle Warehouse Builder 11.2
Oracle Database 11g includes the complete installation of OWB. OWB In-Database functionality is licensed with the Oracle Database while other functionality requires additional licensing. Oracle Database hosts the OWB repository and serves as the transformation engine. Refer to the Oracle Warehouse Builder Installation and Administration guide for details. Installing Oracle Warehouse Builder 11.2 Oracle Database 11g (since Release 1) includes the complete installation of Oracle Warehouse Builder. When you run the Oracle Universal Installer to install the database, OWB is also installed. A preseeded repository, OWBSYS, is created on the database instance. For Oracle Database 10g R2 implementations, you can install the stand-alone version of OWB. All OWB functionality is available and ready to use in each installation. However, the OWB In-Database functionality is licensed with the Oracle Database while other specialized functionality such as data profiling, enterprise ETL require additional licensing. The stand-alone Warehouse Builder is a single installation image that contains both client and server components, which are installed together. If the deployment target database is on a separate machine from the client machine, you need to install the stand-alone version of Warehouse Builder to install the software on a client computer. A client computer is any computer that does not host Oracle Database 11g. If you want to run any Warehouse Builder components on a client computer, including the OMB*Plus scripting utility and the Control Center, you must install the stand-alone software. In other words, you must install the OWB software on any server prior to creating a repository on that machine. Data Integration and ETL with Oracle Warehouse Builder: Part

Simpler OWB 11.2 Installation
Server installation Stand-alone installation DB home DB home OWB 11g stand-alone OWBSYS preseeded OWB 11g server SYSDBA-free setup OWBSYS preseeded Stand-alone installation with DB 10g R2 or 11g R1 Workflow installation files SYSDBA-free setup Workflow installation files OWB Home OWB 11g stand-alone Special scripts Simpler OWB 11.2 Installation The installation of OWB 11.2 is greatly simplified in an Oracle Database 11g environment. When you install the core Database 11g, you get the OWB back end: a preseeded repository schema, OWBSYS. Oracle Workflow installation files are also included in the Oracle Database 11g installation. You need to run the installer to install Oracle Workflow though. Without the requirement of SYSDBA privileges, you can make a sandbox repository and start exploring the OWB tool immediately. Three types of OWB 11g installation are: Server installation as part of the Oracle Database 11g installation Stand-alone installation by using a stand-alone DVD in the database pack Stand-alone installation for Oracle Database 10g R2 or 11g R1 by using special scripts Note: Installing to Oracle Database 10g R2 or 11g R1 requires running two special SQL scripts and a few extra steps, as described later in this lesson. Note For details about installing Warehouse Builder, refer to the Oracle Warehouse Builder Installation and Administration Guide. OWB 11.2 is installed in the same Oracle home as the database. (Requires a few extra steps) Data Integration and ETL with Oracle Warehouse Builder: Part

OWBSYS Schema Stores all the OWB repository objects
Is created as part of every Oracle Database installation Is registered as an OWB user Administrators and developers generally register other database users and assign them required privileges, rather than using the OWBSYS account directly. Needs to be unlocked before any workspace is created OWBSYS (Unified Repository) Single copy of OWB database objects Necessary grants on roles, system and object privileges Eliminates the need for DBA/SYSDBA credentials to define a workspace repository! OWBSYS Schema The OWBSYS schema is created as part of the Oracle Database installation (since 11g Release 1). The OWBSYS schema maintains a single copy of OWB repository objects. It contains the metadata for the database objects such as tables, PL/SQL packages, views, and so on. It also gets the necessary grants on relevant database roles, system and object privileges. As part of the database installation scripting, the OWBSYS schema is seeded as part of these starter databases: General Purpose Transaction Processing Data Warehouse Note: The script that creates OWBSYS is located at: ../owb/UnifiedRepos/cat_owb.sql What Are the Benefits? After database installation, OWB is ready for use. To begin working with your data and metadata, you must define your workspaces, workspace owners, and users, which is discussed later in this lesson. Also, OWBSYS is locked by default. You should unlock it. After you have unlocked the OWBSYS account, the OWBSYS user has the rights for most activities. But you should not use the OWBSYS schema for storing your data or metadata. Data Integration and ETL with Oracle Warehouse Builder: Part

OWB 11.2 Server Installation
DB home OWB 11g server The directory structure looks like this: [ORACLE_HOME]/owb [ORACLE_HOME]/owb/wf OWBSYS preseeded SYSDBA-free setup Workflow installation files OWB 11.2 Server Installation The Oracle Database 11g home contains all the OWB software required to perform the following tasks: Deployment and execution of all standard objects (tables, dimensions, cubes, maps, and so on) Deployment of process flows Warehouse upgrade Run-time scripting Installation of Oracle Workflow The directory structure looks like this: OWB Home: [ORACLE_HOME]/owb Oracle Workflow: [ORACLE_HOME]/owb/wf Data Integration and ETL with Oracle Warehouse Builder: Part

OWB 11.2 Stand-Alone Installation
Reasons for stand-alone installation: To use the Design Client on a developer’s computer To deploy to Oracle Database 10g R2 or 11g R1 with OWB repository hosted on it To run Control Center Agent on a client DB home OWBSYS preseeded SYSDBA-free setup OWB 11g stand alone Workflow installation files OWB 11.2 Stand-Alone Installation You need OWB 11.2 to stand alone only if you need to: Install the OWB software on a client computer A client computer is any computer that does not host the Oracle Database. If you want to run any Warehouse Builder components on a client computer, including the OMB*Plus scripting utility and the Control Center, you must install the stand-alone software. Deploy to a Database 10g R2 or 11g R1 target hosting an OWB repository Run Control Center Agent on a client computer The stand-alone DVD is bundled with the Oracle Database 11g Release 2 pack. To get full functionality, a stand-alone OWB 11.2 must be installed on the database server machine (10g R2 or 11g R1) into a new Oracle home (separate from the database home). It should again be installed on the client to get the Design Center. Note: Oracle Warehouse Builder repositories for version 11.2 and 11.1 cannot coexist on the same database; creating an 11.2 repository destroys all 11.1 repositories on the host. It is recommended that you create a backup of your repositories, and then upgrade 11.1 repositories. If the database contains an Oracle Warehouse Builder 11.1 repository, you must clean it before setting up the 11.2 repository. In other words, you must run clean_owbsys.sql, followed by cat_owb.sql. OWB Home Data Integration and ETL with Oracle Warehouse Builder: Part

Using OWB 11.2 with Database 10g R2
OWB 11.2 assumes the use of Oracle Database 11g Release 2. To use OWB 11.2 with Database 10g R2 or 11g R1: Run a SQL script to create OWBSYS (in 11g R1, first run clean_owbsys.sql to clean the existing OWBSYS schema). Run a SQL script to identify the OWB home to Database 10g R2. Unlock OWBSYS and OWBSYS_AUDIT. OWB 11g stand-alone Using OWB 11.2 with Database 10g R2 OWB 11.2 is architected with an assumption that it is used with Oracle Database 11g Release 2. This tight integration includes preseeding the OWBSYS schema in the default database, and placing OWB in the same Oracle home as the database. To use OWB 11.2 with Database 10g R2 or 11g R1, you must perform a few simple steps. The next slides illustrate those steps: Run a SQL script to create OWBSYS. Run a SQL script to identify OWB home to Database 10g R2 or 11g R1. Unlock OWBSYS and OWBSYS_AUDIT. Note: Starting with Oracle Warehouse Builder 11.1, the metadata repository is stored in the OWBSYS schema, inside a workspace. This contrasts with the terminology of Oracle Warehouse Builder 10.2, where a workspace corresponds to a repository. If the database contains an Oracle Warehouse Builder 11g R1 repository, you must clean it before setting up the 11g R2 repository. To clean the OWBSYS repository, you must run clean_owbsys.sql, followed by cat_owb.sql. The clean_owbsys.sql script is located in [ORACLE_HOME]/owb/UnifiedRepos. The clean_owbsys.sql script drops the contents of any existing OWBSYS schema installations, but leaves the schema otherwise intact. If a previous version of the database is upgraded to 11g, it will not have the OWBSYS schema. OWB home DB home Data Integration and ETL with Oracle Warehouse Builder: Part

Script for Creating OWBSYS in Database 10g R2
Run the SQL command: @[OWB_HOME]/owb/UnifiedRepos/cat_owb <tablespace name>; Specify a dedicated tablespace instead of the USERS tablespace (recommended). Script for Creating OWBSYS in Database 10g R2 If using Database 10g R2, you must run a SQL script to create the OWBSYS repository schema that is needed by OWB (OWBSYS is automatically created during the installation of 11.2.) Connect to SQL*Plus as sysdba and issue the following command to create OWBSYS: @[OWB_HOME]/owb/UnifiedRepos/cat_owb.sql <tablespace_name>; If you do not enter the tablespace name in the command prompt, you will be prompted for a tablespace for the OWBSYS user. Enter a tablespace name and press Enter. It is recommended that you use a dedicated tablespace for your repository instead of using the USERS tablespace. 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.” Data Integration and ETL with Oracle Warehouse Builder: Part

Making OWB Oracle Home Known to Database 10g R2
Run the SQL command: @[OWB_HOME]/owb/UnifiedRepos/ reset_owbcc_home <OWB_HOME>; Specify the full path to the OWB Oracle home. For example: /u01/app/oracle/product/owb112 Making OWB Oracle Home Known to Database 10g R2 Earlier, you were instructed to install Warehouse Builder in an Oracle home other than the database Oracle home, if using OWB 11.2 with Database 10g R2. To ensure access to the Control Center on the 10g R2 database, run the reset_owbcc_home.sql script and pass in your Oracle home for Warehouse Builder. Run the script as a system-privileged user such as SYS or SYSTEM. For example, in a Linux environment, enter the following command at the command prompt, substituting in your own actual OWB path: <OWB_HOME>; If you do not provide the OWB_HOME path on the command line, you are prompted for the full path of the Oracle home for the OWB Control Center installation. On a Windows platform, use slash (/) while entering the <OWB_HOME> path. Note: If you specify the path to the OWB Oracle home incorrectly, the reset_owbcc_home.sql script finishes without apparent errors. However, when you later use the Repository Assistant to create a workspace and users, the process fails. Data Integration and ETL with Oracle Warehouse Builder: Part

Unlock OWBSYS and OWBSYS_AUDIT
Run the following SQL commands: alter user OWBSYS identified by <password> account unlock; alter user OWBSYS_AUDIT identified by <password> account unlock; Unlock OWBSYS and Enable Workspace Access If the strong password option is enabled on the Database, then after creating OWBSYS, you must unlock the OWBSYS account and reset its password. Proceed with the SQL*Plus commands to unlock the OWBSYS account and assign a password: alter user OWBSYS identified by <password> account unlock; You should also unlock the OWBSYS_AUDIT user. This user provides access to the audit tables without needing to connect as owbsys. Note: Additionally, you should check the [OWB_HOME]/owb/bin/admin/Preference.properties file and confirm that the REPOS_DB_VERSION_ALLOWED property is set to Oracle 10g, Oracle 11g. Data Integration and ETL with Oracle Warehouse Builder: Part

Quiz The OWBSYS schema stores the OWB repository objects and is created as part of every new Oracle Database 11g installation. True False Answer: a Data Integration and ETL with Oracle Warehouse Builder: Part

Warehouse Builder Workspace
To define and work with your data and metadata and to use the repository, you must create a workspace. Use the Repository Assistant. Workspace is owned by a workspace owner. Control Center Service Oracle Database instance Repository (OWBSYS schema) OWB Workspace #1 OWB Workspace #2 Warehouse Builder Workspace To begin working with your data and metadata and to use the repository, you must create a workspace. You use the Repository Assistant to create and manage workspaces. A workspace is owned by a workspace owner that has administrative privileges to the workspace. Apart from that, you can create workspace users that have limited access to the workspace. The metadata repository is stored in the workspace inside the OWBSYS schema. Users access their respective workspaces, rather than the repository schema (OWBSYS) as a whole. Many workspace users One workspace owner Data Integration and ETL with Oracle Warehouse Builder: Part

Workspace Installation
Use the Repository Assistant to create a workspace, its owner, and its users. Workspace users’ possible job functions Metadata design Deploying code Executing code - Possible target schema Highly privileged workspace owner - Audit tables - Run-time and deployment statistics - Physical location info Users associated with one workspace Workspace owner (schema with username in the database) Workspace Installation The default installation provides a straightforward workspace structure. The default installation creates a single workspace that handles both design and run-time metadata. Workspace Owner and Workspace Users Each workspace has one highly privileged workspace owner and zero or more users associated with the workspace. Some workspace users may be assigned as warehouse targets for data undergoing the ETL processes. Other users may be used only to connect to Warehouse Builder or to set metadata security and object ownership. As a workspace owner, you can assign additional privileges to workspace users to enable them to perform certain administrative tasks. It is easier to track who performed what tasks if such a user hierarchy is maintained rather than having free access to workspace owner credentials to perform highly privileged tasks. Workspace Owner and Users Created as Database Schemas Workspace owners and users are created using new or existing Oracle database users. The OWB workspace owner name and usernames are thus database schema usernames. Workspace users (schemas with usernames in the database) Data Integration and ETL with Oracle Warehouse Builder: Part

Workspace Owners and Users: Job Functions
Yes No Security, users, and role privileges management Enabled as target schema Administrative tasks (access to run-time/deployment statistics, physical location information, audit details) Deploy and execute code Design metadata (using Design Center) Job Functions WorkspaceOwner Workspace Users The workspace owner can define an intermediate “DBA” role. Users can then be assigned this role, allowing them to perform limited administrative tasks without the privileges of the workspace owner. Workspace Owners and Workspace Users: Job Functions The workspace owner has the Warehouse Builder ADMINISTRATOR role assigned to it, while workspace users are by default granted the Warehouse Builder EVERYONE role. Workspace users have far less database privileges. Their privileges for OWB are controlled by the workspace owner or an administrator. Note that a workspace user can also become an administrator by obtaining the Warehouse Builder ADMINISTRATOR role. OWB workspace owners and users are created using new or existing Oracle database users. The OWB workspace owner name is thus a database schema name. A workspace user cannot perform administrative tasks such as purging run-time audit information and does not have the privileges to manage users, roles, and security settings. A workspace owner can also be used as a target schema. Data Integration and ETL with Oracle Warehouse Builder: Part

Starting the Repository Assistant
On Windows, select Start > Programs > ORACLE_HOME > Warehouse Builder > Administration > Repository Assistant. On Linux, run [ORACLE_HOME]/owb/bin/unix/reposinst.sh. Starting the Repository Assistant The slide explains how you can start the Repository Assistant on Windows and Linux environments. Data Integration and ETL with Oracle Warehouse Builder: Part

Using the Repository Assistant to Manage Workspaces
Each workspace has one workspace owner. Each workspace can have zero or more workspace users. Using the Repository Assistant to Manage Workspaces You use the Repository Assistant to create and manage workspaces, workspace owners, and users. It is also used to: Add display languages to repository: You can have multiple display languages that are associated with business names of your objects. Unlike base languages, you can add display languages after initially defining the repository. For a given object, its physical name corresponds to the base language. However, for each display language you enable, users can create a corresponding business name. Register a Real Application Cluster (RAC) instance Upgrade repository Manage J2EE user account: OWB 11.2 fully supports service-oriented architecture for data integration. It allows J2EE users, who are granted the OWB_J2EE_EXECUTOR role, to execute Web services through a browser. The OWB 10g architecture of multiple repositories is replaced by a single OWBSYS repository schema containing multiple workspaces in OWB11.2. Therefore, design repositories (of previous versions) are now workspaces, repository owners are now workspace owners, and repository users are now workspace users. Data Integration and ETL with Oracle Warehouse Builder: Part

Using the Repository Assistant to Manage Workspaces
DBA credentials are needed if creating a new database user as a workspace owner. Using the Repository Assistant to Manage Workspaces (continued) Prior to OWB 11.2, logging in to the Repository Assistant required SYSDBA credentials. The Repository Assistant no longer requires this highly privileged user. Furthermore, DBA credentials are required only if you are defining a workspace or workspace owner or workspace user with a new database user, rather than an existing one. When the Repository Assistant is run for the first time, you perform the following: Select Tablespaces: The assistant recommends a set of default tablespaces. You can accept the recommendations or specify new tablespaces. Select Languages: The base language is the language of the repository. The physical name for each repository object is assumed to be written in the base language. The Repository Assistant assumes a default base language contingent upon the locale of the machine from which you launched the Repository Assistant. For example, when you run the assistant from a machine with its locale set to British English, the default base language for the repository is en_GB for British English. Data Integration and ETL with Oracle Warehouse Builder: Part

Using the Repository Assistant to Manage Workspaces (continued) You can accept the default or select from a list of base languages. Note: You can define the base language only once. After you create the repository, you cannot change the base language and you cannot add another base language. This means that when users create new repository objects, the physical names are always written in the base language. Note: When you run the Repository Assistant for the first time, it takes more time to create the workspace because during the creation, the repository is also seeded with additional repository objects. Subsequent runs to create workspace are very simple and quick. Data Integration and ETL with Oracle Warehouse Builder: Part

Dropping a Workspace Unregister the associated workspace users before dropping the workspace (recommended). Dropping a Workspace Every workspace may be associated with multiple workspace users. When you drop a workspace, the workspace users become orphans and you cannot use the Repository Assistant to delete them. Therefore, use the Repository Assistant to unregister the associated workspace users before dropping a workspace owner. Alternatively, you can delete the orphan users through SQL*Plus. When you have to drop a workspace that has workspace users associated with it, perform the following recommended steps: In the Choose Operation window, select Manage Warehouse Builder Workspace Users. Click Next. Log in as a workspace owner. Click Next. From the drop-down list, select one of the available workspaces to register or unregister workspace users. Click Next. Select Un-register of Warehouse Builder workspace users. Click Next. In the next window, select the user that you want to unregister and move on until you reach last step. (See the screenshot in the slide.) After you have unregistered the users, go back to the Choose Operation window and select Manage Warehouse Builder workspaces. In the Choose Workspace Operations window, select Drop an existing Warehouse Builder workspace. (See the screenshot in the slide.) Data Integration and ETL with Oracle Warehouse Builder: Part

OWB Product Components
Design Center (owbclient.sh/bat) Repository Assistant (reposinst.sh/bat) OMB*Plus scripting client (OMBPlus.sh/bat) Start/stop Repository Browser OC4J Server ([startOwbInst.sh/bat/][stopOwbInst.sh/bat]) Start Repository Browser (openRAB.sh/bat or openDB.sh/bat) Start stand-alone Control Center Service (run_service.sh/bat) Start/stop Control Center Agent ([ccastart.sh/bat]/[ccashut.sh/bat]) Control Center Agent Administration (cca_admin.sh/bat) OWB Product Components This slide shows the range of components that make up the OWB product. After successfully installing the Warehouse Builder software, you should see the product components added to your Programs menu on Windows. On Linux, you should browse to the [ORACLE_HOME]/owb/bin/unix folder to run the relevant shell script (.sh) as mentioned in the slide. Note: To start the Repository browser, openRAB.sh defaults to the run-time reports and openDB.sh defaults to the design reports. You use run_service.sh when you want to run the control center service on a different machine from the server hosting OWB. Data Integration and ETL with Oracle Warehouse Builder: Part

Lesson Agenda Oracle Warehouse Builder: Introduction Oracle Warehouse Builder Installation OWBSYS schema Server and stand-alone installation Installing on Database 10g R2 or 11g R1 Workspace, Workspace Owners, and Users Using the Repository Assistant Supported operating systems (OS), sources, targets, and optional components Classroom Configuration and Documentation Resources Data Integration and ETL with Oracle Warehouse Builder: Part

Supported Operating Systems
Oracle Warehouse Builder 11g Release 2 (11.2) is available on the same platforms supported by Oracle Database 11g Release 2 The Design Center client is supported on both Windows(32 bit) and Linux (32 bit). For an updated list of certified hardware platforms and operating-system versions, review the certification matrix on My Oracle Support. Supported Operating Systems Oracle Warehouse Builder 11g Release 2 (11.2) is available on the same platforms supported by Oracle Database 11g Release 2. Oracle Warehouse Builder 11g Release 2 (OWB 11.2) is available on the Windows (XP or 2000) and Linux (32 bit). Note that Design Center client is supported only on Windows(32) and Linux(32); For more details on the supported platforms, review the certification matrix on My Oracle Support. Note: For memory requirements and environment settings for a particular operating-system platform, refer to the Oracle Warehouse Builder Installation and Administration Guide. Data Integration and ETL with Oracle Warehouse Builder: Part

Oracle Database Support: Source, Target, Repository
Oracle Database is the earliest Oracle version to which Warehouse Builder 11g Release 2 can connect as a source. Oracle Database 11.2 is recommended for the Warehouse Builder 11g Release 2 repository schema, OWBSYS. If you have to use Oracle Database 10g R2 or 11g R1, perform the extra steps discussed in previous slides. Oracle Database XE is not supported (no Java in the database). Oracle Database Support: Source, Target, Repository Oracle Database version 11.2 (or later) is recommended for the Warehouse Builder 11g Release 2 repository schema, OWBSYS. However, you can use the Oracle Database 10g R2 or 11g R1 for the OWBSYS repository schema. Data Integration and ETL with Oracle Warehouse Builder: Part

Installing Optional Components
Supported Versions Oracle Workflow Oracle Workflow (included in the database installation in the [ORACLE HOME]/owb/wf folder) Oracle Job Scheduler Oracle has a built-in DBMS Scheduler that can be used to deploy Warehouse Builder schedules or to create new scheduled jobs. Third-Party Name and Address Data You need the following from one of the certified vendors listed on Oracle Technology Network: Regional data libraries Name and address adapter software Business Intelligence (BI) tools Oracle Business Intelligence Enterprise Edition (OBI EE) Oracle Business Intelligence Standard Edition (OBI SE) Installing Optional Components Oracle Workflow Oracle Workflow is used to manage job dependencies. If you plan to use Warehouse Builder process flows, you need Oracle Workflow to enable deployment. Oracle Workflow is included in the database installation in the [ORACLE HOME]/owb/wf folder. More details are provided in the slide that follows. Oracle Job Scheduler The RDBMS has a built-in job scheduler and you model and deploy schedules in OWB for this scheduler. You can use Oracle Workflow to manage dependencies for jobs that reside in the DBMS Job Library. You can also use the Oracle-supplied DBMS_SCHEDULER package to administer scheduling capabilities. You can create a scheduled job for a mapping by using the DBMS_SCHEDULER.CREATE_JOB( ) template, or you can go through the DBMS_SCHEDULER jobs in Enterprise Manager and create schedules for your process flows or mappings. You can also use any third party scheduler to invoke OWB mappings and process flows. Now that you can easily publish OWB design items as Web services, they can also be easily integrated in SOA environments. Data Integration and ETL with Oracle Warehouse Builder: Part

Installing Optional Components (continued) Third-Party Name and Address Data Warehouse Builder enables you to work with your preferred data quality vendor for its basic data cleansing functionality. The Warehouse Builder application-programming interfaces (APIs) are available to specialized data quality vendors. Refer to for a list of preferred partners to download data libraries. Install Business Intelligence (BI) Tools For BI tools, Oracle supports Oracle Business Intelligence Enterprise Edition (EE) and Oracle Business Intelligence Standard Edition One as well as partner solutions. Data Integration and ETL with Oracle Warehouse Builder: Part

Simplified Installation of Oracle Workflow
In Database 11g environment In a DB 10g environment DB 11g OWB 11g stand alone DB 10g R2 OWB 11g server install Workflow install files in [OWB_HOME]/owb/wf/install + Workflow installation files in [ORACLE_HOME]/owb/wf/install (contains a version of WF with changes for 11g) Simplified Installation of Oracle Workflow If you want to use Oracle Workflow to manage job dependencies or if you want to deploy process flows, it is necessary to install Oracle Workflow. For Database 11g, use the Workflow installation files provided in the database installation owb/wf folder. This installs a special version of Workflow with changes specifically for Database 11g. For Database 10g R2, the required Workflow installation files are provided with the Oracle Warehouse Builder installation in the following directory: [OWB_HOME]/owb/wf To start the installation and configuration on Linux: In a Linux terminal window, change to the [ORACLE_HOME]/owb/wf/install directory, and run wfinstall.csh. To start the installation and configuration on Linux: Run wfinstall.csh located in the [ORACLE_HOME]/owb/wf/install directory. Data Integration and ETL with Oracle Warehouse Builder: Part

Simplified Installation of Oracle Workflow (continued) Workflow Installation and Configuration To start the installation and configuration script on Windows: In a command prompt window, change to the [ORACLE_HOME]\owb\wf\install directory, and run wfinstall.bat. For example: C:\> cd [oracle_home]\owb\wf\install C:\owb_home\owb\wf\install> wfinstall.bat To start the installation and configuration script on Linux: In a UNIX shell, change to the [ORACLE_HOME]/owb/wf/install directory, and run wfinstall.csh. For example: $ cd [ORACLE_HOME]/owb/wf/install $ wfinstall.csh The Workflow Configuration Assistant dialog box appears. Specify the following values: For Install Option, select Server Only. For Workflow Account, enter owf_mgr. For Workflow Password, enter your chosen password for the Workflow Account. 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 the necessary values, click Submit to start the Workflow configuration process. The configuration process can take several minutes. Check [ORACLE_HOME]/owb/wf/install/workflow.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. Data Integration and ETL with Oracle Warehouse Builder: Part

Lesson Agenda Oracle Warehouse Builder: Introduction Oracle Warehouse Builder Installation: OWBSYS schema Server and stand-alone installation Installing on Database 10g R2 or 11g R1 Workspace, Workspace Owners, and Users Using the Repository Assistant Supported operating systems (OS), sources, targets, and optional components Classroom configuration and Documentation Resources Data Integration and ETL with Oracle Warehouse Builder: Part

Classroom Configuration
Gnome Linux in an Oracle VM Access the environment using NOMachine Oracle Database 11g Release 2 Service name (SID) is orcl.oracle.com Workflow Server is installed and configured owf_mgr is the workflow schema. You will create the following in the practice: Workspace Name: workspace1 Workspace Owner: owb1 (used to login in the client) Workspace User: owb1_user Classroom Configuration This slide describes the classroom setup. You will use the NoMachine (also called NX client) client to connect to the Oracle VM environment. Data Integration and ETL with Oracle Warehouse Builder: Part

Oracle Warehouse Builder Documentation and Resources
Oracle Warehouse Builder on OTN Reference Guides: Oracle Warehouse Builder Installation and Administration Guide Oracle Warehouse Builder Concepts Oracle Warehouse Builder Sources and Targets Guide Oracle Warehouse Builder ETL and Data Quality Guide Oracle Warehouse Builder Release Notes Oracle Warehouse Builder Documentation and Resources Navigate to the online Oracle Database 11.2 Documentation Library using the following URL: Expand the “Data Warehousing and Business Intelligence” navigation folder and click the Oracle Warehouse Builder link to access the documentation. You can post your queries and look for common errors and their solutions on the discussion forums accessible from the Oracle Warehouse Builder page on OTN. Data Integration and ETL with Oracle Warehouse Builder: Part

Quiz Which of the following tasks does the Repository Assistant wizard perform? Creates a new workspace, workspace owner, and users Creates the OWBSYS schema if the database is 10g Drops workspace Unregisters workspace users Answer: a, c, d Data Integration and ETL with Oracle Warehouse Builder: Part

Summary In this lesson, you should have learned how to: Describe Oracle Warehouse Builder (OWB) Explain the OWB In-Database and identify other licenses Identify a variety of possible installation configurations Identify the supported sources and targets Create the workspace and the workspace users Data Integration and ETL with Oracle Warehouse Builder: Part

Practice 1-1 Overview: Creating a Workspace, Workspace Owner, and a Workspace User This practice covers creating a workspace, workspace owner and user by using the Repository Assistant. Practice 1-1 Overview: Creating a Workspace, Workspace Owner, and a Workspace User In this practice, you create a workspace and its associated users. This workspace is used throughout the course. Data Integration and ETL with Oracle Warehouse Builder: Part

Installing and Setting Up the Warehouse Builder Environment

Similar presentations

Presentation on theme: "Installing and Setting Up the Warehouse Builder Environment"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Installing and Setting Up the Warehouse Builder Environment

Similar presentations

Presentation on theme: "Installing and Setting Up the Warehouse Builder Environment"— Presentation transcript:

Similar presentations

About project

Feedback