Skip Headers
Oracle® Warehouse Builder Installation and Administration Guide
11g Release 2 (11.2) for Windows and Linux

Part Number E10579-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

6 Migrating Oracle Warehouse Builder from Earlier Releases

Oracle Warehouse Builder enables you to upgrade repositories from earlier versions of Oracle Warehouse Builder10g Release 2 and Oracle Warehouse Builder 11g Release 1 to Warehouse Builder 11g Release 2. This section describes how to perform this upgrade.

To upgrade from versions of Oracle Warehouse Builder earlier than 10g Release 2, you must first upgrade to Oracle Warehouse Builder 10g Release 2 or Oracle Warehouse Builder 11g Release 1. You may then upgrade your repository to Oracle Warehouse Builder 11g Release 2.

Note that during the repository upgrade, the Design Metadata and Control Center Agent audit data is automatically moved to the OWBSYS schema.

This section includes the following topics:

Migrating the Repository on the Same Database Instance

You can perform an in-place upgrade of either a 10g R2 or 11g R1 repository that exists on the same database instance as your Oracle Database 11g R2 installation.

To preform the tasks in this section, you must have SYSADMIN privileges, which allow you to execute prerequisite scripts. Note that before you start the actual migration using the Repository Assistant, you should prepare by backing up the current OWBSYS schema, creating an OWBSYS schema if it does not exist (10g R2) or upgrade it (11g R1), and resetting OWB_HOME on the new instance. Note that you would also need to unlock the OWBSYS and OWBSYS_AUDIT schemas.

Also note that the repositories from versions earlier than 10g R2 cannot be upgraded to 11R2 directly; they must be first upgraded to 10g R2.

Preparing for Repository Migration

The steps for preparing a repository for migration are separate for Windows and Linux.

To prepare for a repository upgrade on Windows:

  1. Ensure that you make a back-up copy of the OWBSYS schema, using the backup strategy employed in your organization.

  2. On the Microsoft Windows desktop, click Start and select Run.

  3. In the Run window, for Open, enter cmd.

    Click OK.

  4. At the command prompt, start SQL*Plus:

    C:\>sqlplus
    SQL*Plus: Release 11.2 - Production on Mon July 27 16:24:02 2009
     
    Copyright (c) 1982, 2009, Oracle.  All rights reserved.
     
    
  5. Connect as user with administrative privileges:

    SQL> connect sys as sysdba
    Enter password: password
    
  6. You have two options for the OWBSYS schema:

    • If the OWBSYS schema does not exist on the Oracle Database instance, run the cat_owb.sql script to create it:

      SQL> @C:\OWB112\owb\UnifiedRepos\cat_owb.sql
      
    • If the OWBSYS schema exists on the Oracle Database instance, and you are upgrading from OWB 11g Release 1, run the cat_owb_reposupgrade.sql script to upgrade it:

      SQL> @C:\OWB112\owb\UnifiedRepos\cat_owb_reposupgrade.sql
      
  7. Run the reset_owbcc_home.sql script to reset the OWB_HOME directory:

    SQL> @C:/OWB112/owb/UnifiedRepos/reset_owbcc_home.sql
    

    Note that this entry is case-sensitive, does not accept a trailing slash, and requires forward slashes only, regardless of the operating system.

To prepare for a repository upgrade in Linux:

  1. Ensure that you make a back-up copy of the OWBSYS schema, using the backup strategy employed in your organization.

  2. At the command prompt, start SQL*Plus:

    % sqlplus
    SQL*Plus: Release 11.2 - Production on Mon July 27 16:37:21 2009
    
    Copyright (c) 1982, 2009, Oracle.  All rights reserved.
    
  3. Connect as user with administrative privileges:

    SQL> connect sys as sysdba
    Enter password: password
    
  4. You have two options:

    • If the OWBSYS schema does not exist on the Oracle Database instance, run the cat_owb.sql script:

      SQL> @OWB112/owb/UnifiedRepos/cat_owb.sql
      

      You are prompted for the tablespace name; enter it.

    • If the OWBSYS schema exists on the Oracle Database instance, and you are upgrading from OWB 11g Release 1, run the cat_owb_reposupgrade.sql script:

      SQL> @OWB112/owb/UnifiedRepos/cat_owb_reposupgrade.sql
      

      You are prompted for the tablespace name; enter it.

  5. Run the reset_owbcc_home.sql script to reset the OWB_HOME directory:

    SQL> @OWB112/owb/UnifiedRepos/reset_owbcc_home.sql
    

    Note that this entry is case-sensitive, does not accept a trailing slash, and requires forward slashes only, regardless of the operating system.

  6. Unlock the OWBSYS and OWBSYS_AUDIT accounts, as described in the following sections:

Upgrading an OWB 11g R1 Repository

When upgrading from an OWB 11g R1 repository, you are upgrading an existing OWBSYS schema on an existing repository.

To perform an in-place repository upgrade of an 11g R1 repository:

  1. Start the Repository Assistant.

    In Windows, from the Start menu, select Program Files, then Oracle - OWB112, then Warehouse Builder, then Administration, then Repository Assistant.

    In Linux, from the command line, run OWB_HOME/owb/bin/unix/reposinst.sh.

  2. On the Welcome page of the Repository Assistant, click Next.

  3. On the Database Information page, enter the host name, port number, and the service name where the OWB is installed.

    Surrounding text describes upgrade_00.gif.

    Click Next.

  4. On the Choose Operation page, select Upgrade repository to current release of Oracle Warehouse Builder.

    Description of upgrade_01.gif follows
    Description of the illustration upgrade_01.gif

    Click Next.

  5. On the Choose Upgrade Operations page, select Upgrade repository on the same database instance.

    Description of upgrade_02.gif follows
    Description of the illustration upgrade_02.gif

    Click Next.

  6. On the OWBSYS Information page, enter the password for the OWBSYS user.

    Description of upgrade_03.gif follows
    Description of the illustration upgrade_03.gif

    Click Next.

  7. On the File Information page, in the Directory Name field, specify the name of the existing directory used for storing *.mdl files, log files, and other temporary files used during repository upgrade.

    Description of upgrade_04.gif follows
    Description of the illustration upgrade_04.gif

    Click Next.

  8. On the Summary page, click Finish to complete the upgrade process. Description of upgrade_05.gif follows
    Description of the illustration upgrade_05.gif

  9. The Installation Progress popup window indicates the progress of the upgrade operation. When complete, click OK.

Upgrading an OWB 10g R2 Repository

You can upgrade a 10g R2 repository by exporting its content to a file, and then importing the file into an 11g R2 repository, using the Repository Assistant.

Exporting a Repository to a File

To export a repository to a file:

  1. Start the Repository Assistant.

    In Windows, from the Start menu, select Program Files, then Oracle - OWB112, then Warehouse Builder, then Administration, then Repository Assistant.

    In Linux, from the command line, run OWB_HOME/owb/bin/unix/reposinst.sh.

  2. On the Welcome page of the Repository Assistant, click Next.

  3. On the Database Information page, enter the host name, port number, and the service name where the OWB is installed.

    Click Next.

  4. On the Choose Operation page, select Upgrade repository to current release of Oracle Warehouse Builder.

    Description of upgrade_01.gif follows
    Description of the illustration upgrade_01.gif

    Click Next.

  5. On the Choose Upgrade Operation page, select Export entire repository to a file.

    Description of export_01.gif follows
    Description of the illustration export_01.gif

    Click Next.

  6. On the User Information page, enter the user name and password of the 10g R2 repository owner.

    Description of export_02.gif follows
    Description of the illustration export_02.gif

    Click Next.

  7. On the File Information page, fill these fields:

    • File Name: the name of the MDL file for storing the repository.

    • Log File: the name of the export operation log file that stores status and statistical information.

    Description of upgrade_04.gif follows
    Description of the illustration upgrade_04.gif

    Click Next.

  8. On the Summary page, click Finish.

    An Export Repository Progress window appears showing progress.

    At the end of the export process, a status message appears. The export operation creates the file.

Importing a File into a Repository

To import a file into a repository:

  1. Start the Repository Assistant.

    In Windows, from the Start menu, select Program Files, then Oracle - OWB112, then Warehouse Builder, then Administration, then Repository Assistant.

    In Linux, from the command line, run OWB_HOME/owb/bin/unix/reposinst.sh.

  2. On the Welcome page of the Repository Assistant, click Next.

  3. On the Database Information page, enter the host name, port number, and the service name where the OWB is installed.

    Click Next.

  4. On the Choose Upgrade Operation page, select Import entire repository from file.

    Description of import_02.gif follows
    Description of the illustration import_02.gif

    Click Next.

  5. On the OWBSYS Information page, enter the password.

    Description of import_01.gif follows
    Description of the illustration import_01.gif

    Click Next.

  6. On the File Information page, enter or browse to find the name of the files used when exporting the repository.

    Description of upgrade_04.gif follows
    Description of the illustration upgrade_04.gif

    Click Next.

  7. On the Summary page, click Finish.

    The file is imported into a workspace that has the same name as the 10g R2 OWB repository.

Migrating the Repository to a Different Oracle Database Instance

The process of migrating the repository to a different Oracle Database instance involves the export of the existing repository to file, and subsequent import of information from that file into a new repository on the other Oracle Database instance.

This process is virtually identical to upgrading from an OWB 10g R2 repository to a current version of the repository. The main difference is that at the time of importing, you would be providing the credentials of a remote Oracle Database instance where the export files reside.

Exporting a Repository

The export part of the scenario uses the Repository Assistant to create an MDL zip file. This MDL zip includes information about all the workspaces in the repository, with each workspace stored as a separate file.

The export operation is described in section "Exporting a Repository to a File".

Importing a Repository

Before importing the repository, in the target Oracle Database instance that contains the migrated repository, create the same users who had access to the original repository. You must do this to ensure that the security information is correctly imported. However, you do not need to create these users as OWB users; the upgrade process handles this automatically.

The import operation is described in section "Importing a File into a Repository". Note that in step 6, you are entering the credential of the source (remote) database, which contains the repository MDL and log files.

Upgrading Locations

To upgrade the locations, use the Oracle Warehouse Browser Location Report and Locations Report in the Oracle Warehouse Browser.

  1. In Oracle Warehouse Builder, select Control Center.

    Click Reports.

  2. In the Reports window, under Deployment, click Locations Reports.

    Description of locations_01.gif follows
    Description of the illustration locations_01.gif

  3. On the Locations Report, under Logical Details, in the Validation column of the table, click Unknown.

    Description of locations_02.gif follows
    Description of the illustration locations_02.gif

  4. Under Connection details, because the status is Unknown, enter the Password and click Get Status.

    Description of locations_03.gif follows
    Description of the illustration locations_03.gif

    Note that the Current Status is Invalid.

  5. Under Location Status, click Upgrade.

    Description of locations_04.gif follows
    Description of the illustration locations_04.gif

    Note that the Current Status is Valid.

  6. Repeat steps 3 through 5 for all installations.

  7. Once you are finished, notice that the Validation column shows Tested locations

    Description of locations_05.gif follows
    Description of the illustration locations_05.gif