Upgrading from Warehouse Builder to 10.2.0.5

 Upgrading from Warehouse Builder to 10.2.0.5 

Pre-Installation

Before you install this patch, check the following:

·         On Unix-based platforms, you must be logged in as the UNIX user that owns the Oracle Warehouse Builder installation before performing the patch install.

·         Stop and exit all Warehouse Builder components, including the Control Center Service, known as the Runtime Platform Service in Warehouse Builder 10.1 and earlier releases.

To stop the Control Center, run the stop_service.sql script. In SQL*Plus, execute the following command:

sqlplus owb_owner/owb_owner @owb home/owb/rtp/sql/stop_service.sql

A return value of Not Available indicates that you successfully stopped the service.

·         If you applied DST patch 5921358 to your Warehouse Builder 10g Release 2 (10.2) installation, you must add write permissions to the owb home/jdk directory.

In Unix, use the command prompt to navigate to the owb home/jdk directory and execute the following command:

chmod -R +w *

In Windows, use the Windows Explorer to perform the following steps:

1.      Right-click the owb home\jdk directory and select Properties.

2.      In the Attributes section, clear Read-only.

3.      Click Apply.

Upgrading from Warehouse Builder 10.2.0.1, 10.2.0.2, 10.2.0.3, or 10.2.0.4

Without deinstalling the existing Warehouse Builder software, install the Warehouse Builder 10.2.0.5 patch into the existing Warehouse Builder 10.2 home directory.

To install the patch take the following steps:

1.      Using WinZip, extract the archive into a temporary directory on your local system. For example, such as C:\OWB10205.

2.      Use WinZip to open the archive file. Be sure to enable the option Use Folder Names.

3.      Run the Oracle Universal Installer from the Warehouse Builder home directory.

For Windows, launch owb home\oui\bin\setup.exe.

For Linux, launch owb home\oui\bin\runInstaller.sh.

4.      Follow the prompts in the Oracle Universal Installer.

For the source location, specify Disk1\stage\products.xml located under the temporary directory you created in step 1.

For the home details, specify the home directory of the existing Warehouse Builder 10.2 installation.

5.      Navigate to the appropriate execution directory under the Warehouse Builder home directory and run the upgrade utility. The specific file you should execute depends on the release of the Oracle Database you are running.

For Windows, the .bat files are located under the win32 directory. If your Oracle Database is either 9iR2 or10gR1 run the following:

owb home/owb/bin/win32/DTupg102to10205_10gR1.bat

Or, if your Oracle Database is 10gR2 or 11g, run the following:

owb home/owb/bin/win32/DTupg102to10205_10gR2.bat

For UNIX, the .sh files are located under the unix directory. If your Oracle Database is either 9iR2 or 10gR1, run the following:

owb home/owb/bin/unix/DTupg102to10205_10gR1.sh

Or, if your Oracle Database is 10gR2 or 11g, run the following:

owb home/owb/bin/unix/DTupg102to10205_10gR2.sh

6.      Enter the database connection information, the Warehouse Builder repository owner credentials, and the SYS user credentials.

The upgrade utility proceeds to upgrade the Warehouse Builder objects associated with the selected repository owner.

The upgrade utility logs any errors in the file owb home/owb/reposasst/upg/LOG.TXT. Note that you can ignore any creation errors reported due to objects already existing.

DROP TABLE dataflow_dependency_t

ERROR at line 1:

ORA-00942: table or view does not exist

CREATE TABLE alldataflow_dependency_t (

ERROR at line 1:

ORA-00955: name is already used by an existing object

7.      Refer to the "Known Issues and Limitations" section for a list of limitations concerning the "Upgrade" process.

For certain upgrade scenarios, you may need to take additional steps.

8.      Repeat steps 5, 6 and 7 for each repository owner.

9.      The  Control Center Service should be running after performing the repository migration.  You can use the service_doctor.sql script to confirm.

sqlplus owb_owner/owb_owner @owb home/owb/rtp/sql/service_doctor.sql

All PL/SQL packages and functions are valid

Platform properties have been loaded correctly

Platform location has been seeded correctly

NLS messages have been loaded correctly

The platform service is available

Service script is accessible to the database server

Connection information stored within the repository is correct

If the service fails to start after two attempts, run the start_service.sql script to restart

sqlplus owb_owner/owb_owner @owb home/owb/rtp/sql/start_service.sql

A return value of Available indicates that you successfully started the service. If the service fails to start, run the start_service.sqlscript again to identify the problem.

If you encounter an obfuscation error when attempting to start the Control Center Service, run the script owb home/owb/rtp/sql/reset_repository.sql.

Note : All the above information is taken from oracle metalinks to make easy search.

Installing OWB on Oracle Database 11g Release 2

Installing OWB on Oracle Database 11g Release 2

Working with the OWB Standalone Install Package

To obtain Oracle Warehouse Builder standalone software:

1. Navigate the browser to the following URL:

http://www.oracle.com/technology/products/warehouse/

2. On the right side of the page, click All Releases and Platforms.

3. Under Oracle Warehouse Builder Downloads, select Accept for the licence agreement.

The system displays the following message: "Thank you for accepting the OTN License Agreement; you may now download this software."

4. Under the Standalone Software download, click the down arrow beside the platform of your choice to download the ZIP file that contains Oracle Warehouse Builder.

For Windows: choose the Microsoft Windows option. For Linux: choose the Linux x86 option.

5. When the download is complete, extract the ZIP file into a temporary directory.

For example,

For Windows: use C:\temp\OWB.

For Linux: use /temp/OWB.

Installing Oracle Warehouse Builder through Oracle Universal Installer

To run Oracle Universal Installer:

1. In Windows Explorer, navigate to the directory that contains the extracted Oracle Warehouse Builder installation files. In this discussion the sample directory is

C:\temp\OWB.

2. Click the setup.bat file to start the Universal Installer.

3. On the Welcome screen, click Next.

4. On the Specify Home Details screen, specify a new Oracle Home:

■ Enter the Oracle Home Name; for example, OWB112.

■ Enter or browse to Path C:\.

■ Click Next.

Tip: To ensure a successful installation:

■ Do not use an existing Oracle Home.

■ Do not use any spaces in the directory path.

5. [Optional] On the Customer Support Email screen, enter the Email and Password

for your My Oracle Support account.

Click Next.

6. On the Summary screen, click Install.

7. The Install screen shows progress during the installation process.

8. At the End of Installation screen, click Exit. The Exit message appears asking if

you really want to exit.

9. In the Exit message, click Yes.

Migrating Oracle Warehouse Builder from Earlier Releases

Migrating Oracle Warehouse Builder from

Earlier Releases

Note that before you start the actual migration using the Repository Assistant, you should prepare by backing up the current OWBSYS schema, Also note that the repositories from versions earlier than 10g R2 cannot be upgraded to

11g R2 directly; they must be first upgraded to 10g R2.

Preparing for Repository Migration

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

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.

Performing the In-Place Repository Upgrade

When upgrading from an OWB 11g R1 repository, you are upgrading an existing OWBSYS schema on an existing repository. When upgrading from OWB 10.2, your upgrade process will create a new workspace in the OWB 11.2 repository, with the same name as the schema containing the OWB 10.2 repository. In either case, the process is similar.

To perform an in-place repository upgrade 

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 service name where OWB is installed.

Description of the illustration upgrade_00.gif

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.    The File Information page appears. The in-place repository upgrade process creates a repository export MDL file. The default file names and location for this exported MDL file and export log file are displayed here. You can change the location of these files.

Description of the illustration upgrade_04.gif

Click Next to accept the file information.

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

You may wish to review the log for errors, and save the exported MDL file as a backup of your pre-upgrade repository.

Exporting a Repository to a File

To export a repository to a file:

1. Start the 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.

Click Next.

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

Click Next.

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

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.

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.

Click Next.

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

Click Next.

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

when exporting the repository.

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.

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.

Click Next.

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

database instance.

Click Next.

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

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.

Click Next.

8. On the Summary page, click Finish to complete the upgrade process.

9. The Installation Progress popup window indicates the progress of the upgrade

operation. When complete, click OK.