6 Migrating Oracle Warehouse Builder from Earlier Releases

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:

   • For Windows, "Unlocking the OWBSYS and OWBSYS_AUDIT Accounts"

   • For Linux, "Unlocking the OWBSYS and OWBSYS_AUDIT Accounts"

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.

   
   

   Click Next.

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

   
   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 the illustration upgrade_02.gif
   
   

   Click Next.

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

   
   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 the illustration upgrade_04.gif
   
   

   Click Next.

8. On the Summary page, click Finish to complete the upgrade process.
   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

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.