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.