| Oracle9i Warehouse Builder Installation and Configuration Guide Release 9.2.0.3 Part Number B11000-02 |
|
This chapter discusses the hardware and software requirements for an Oracle9i Warehouse Builder installation. This chapter includes the following topics:
These high-level installation steps are for experienced Warehouse Builder installers. If you have installed Warehouse Builder before, and if your system hardware and software already conforms to the Oracle9i Warehouse Builder installation requirements, you can follow the steps in this section and use the rest of this manual for reference only.
|
Note: The installation quick steps are not recommended for first-time installers. If you are not an experienced Warehouse Builder installer, please read this entire chapter to ensure that your system conforms to Warehouse Builder installation requirements, and then proceed to Chapter 2, "Installing Oracle9i Warehouse Builder Components" to ensure that you make the proper installation choices. |
This section contains a short description of the installation steps. The rest of this chapter discusses the system and environment requirements for a successful Warehouse Builder installation. For expanded information about each parameter and for instructions on installing optional components, refer to the detailed installation instructions Chapter 2, "Installing Oracle9i Warehouse Builder Components".
High-Level steps to install Oracle9i Warehouse Builder:Step 1. Perform the OWB Design Time Install using Oracle Universal Installer:
setup.exe.
ORACLE_HOME destination.
Step 2. Install the Design Repository using the Repository Assistant:
Step 3. Enable Warehouse Builder Design Browser Client:
Go to http://hostname:port/
For port, 7777 is the default on UNIX platforms; 80 is the default on Windows platforms, or as specified during installation. If you have multiple installations of Oracle HTTP Server on the same host, the port number is typically increased by one for each additional installation. Refer to the Oracle HTTP Server documentation for more information.
Select mod_plsql, then Gateway Database Access Descriptor Settings, and then Add Default (blank configuration).
Enter the Database Access Descriptor Name: use the Warehouse Builder Repository Schema Name. Under Database Connectivity Information, enter the User Name and Password for the schema in which your design repository is located. Enter the Oracle Connect String: HOST:PORT:SID to point to Warehouse Builder Repository instance. Leave other fields blank.
Step 4. Perform the OWB Server Side Install using Oracle Universal Installer:
setup.exe.
ORACLE_HOME destination.
Step 5. Install Runtime Objects Using the Runtime Assistant:
Step 6. Configure the Web Browser for Design and Runtime Audit Browsers:
Oracle9i Warehouse Builder is an integrated system for the design, implementation, and management of an enterprise-wide data warehouse or data mart. Warehouse Builder provides the framework to create your data warehouse and populate it from your existing Oracle products as well as other non-Oracle data sources. You can use Warehouse Builder to create a logical model of your data warehouse and generate code to extract, transform, and load the data into your data warehouse.
The Warehouse Builder architecture consists of the components shown in Figure 2-1. A detailed explanation of this diagram is included in Section 2.1.1, "Warehouse Builder Architectural Components".
A complete, working Oracle9i Warehouse Builder environment includes the software and components in Table 1-1.
You can install these components in any order, using the Oracle Universal Installer (OUI). Here are a few recommendations:
ORACLE_HOME, and service name must be tailored to your installation requirements.
You need the Oracle 8.1.7 or Oracle9i database to install the Warehouse Builder Repository, the Warehouse Builder Runtime Repository, and optionally, the OEM Repository.
To use the Warehouse Builder Design client or Runtime Audit Browser, you need to:
Install Oracle9i Application Server (Oracle9iAS) if you want to run the Warehouse Builder Design or Runtime Audit Browser on an application server. The required Oracle9iAS components are:
These components are required only if you wish to integrate Warehouse Builder Design Browser or the Warehouse Builder Runtime Audit Browser with it. The Design Browser can be used to view your metadata and run metadata web reports; the Runtime Audit Browser can be used to view your runtime audit results.
Integrating the Design and Runtime Audit Browsers with Oracle9iAS is optional. Oracle9i Warehouse Builder also provides client versions of the Design Browser and Runtime Audit Browser. These client versions of Warehouse Builder Design Browser and Runtime Audit Browser are included in the Warehouse Builder repository installation, and only require minor setup.
The Warehouse Builder client software includes the client side repositories and browsers. During the install, you can create the Warehouse Builder Design Repository, the Warehouse Builder Runtime Repository, and the Warehouse Builder Browser tables in your database.
The Warehouse Builder Client consists of:
Repository Assistant: Enables you to create your Warehouse Builder Design Repository.
Runtime Assistant: Enables you to create your Warehouse Builder Runtime Repository.
Browser Assistant: Enables you to create Warehouse Builder Browser tables in your Oracle9iAS database. This is optional.
Oracle Metabase (OMB) Plus: Enables you to interact with Warehouse Builder through scripting commands, outside of the graphic user interface.
You can use Oracle Enterprise Manager (OEM) to schedule jobs and Oracle Workflow (OWF) to manage job dependencies. The OEM Change Management Pack is also used for life cycle management of a data warehouse. This pack is installed as part of the Runtime Repository when you run the Oracle9i Warehouse Builder Runtime Repository Assistant.
You must observe the requirements in Table 1-2 to install the Warehouse Builder Design Time and the Warehouse Builder Server Side components.
Memory requirements increase depending on the functions being performed and the number of users connected. You must also make sure you have ample swap space.
This section contains software requirements for each operating system on which Oracle9i Warehouse Builder is certified. In this section:
Table 1-3 contains the Windows operating environment software requirements for installing Oracle9i Warehouse Builder.
| Software Item | Requirement |
|---|---|
|
Windows Operating Environment |
Table 1-4 contains the Solaris operating environment software requirements for Oracle9i Warehouse Builder. The Solaris operating environment patches can be downloaded from:
http://java.sun.com/j2se/1.3/install-solaris-patches.html
Table 1-5 contains the HP-UX operating environment software requirements for Oracle9i Warehouse Builder. The HP-UX operating environment patches can be downloaded from http://www.hp.com.
| Software Item | Requirement |
|---|---|
|
HP-UX Operating Environment |
|
|
Operating System Patches |
|
|
Software |
|
|
Required Executables |
Table 1-6 contains the Linux operating environment software requirements for Oracle9i Warehouse Builder. You can download Red Hat patches from http://www.redhat.com.
| Software Item | Requirement |
|---|---|
|
Linux Operating Environment |
|
|
Operating System Patches |
|
|
Required Executables |
|
|
Software |
Table 1-7 contains the AIX operating environment software requirements for Oracle9i Warehouse Builder.
| Software Item | Requirement |
|---|---|
|
AIX Operating Environment |
|
|
Operating System Patches |
|
|
Required Executables |
Table 1-8 lists the software requirements for each Warehouse Builder component.
| Warehouse Builder Component | Software Requirements |
|---|---|
|
Warehouse Builder Design Time (Client Software) |
Warehouse Builder repository requires Oracle 8.1.7 or Oracle9i Database Server Release 1 or 2. Note: Use this version with a newly created Warehouse Builder repository. Do not use a previously created Warehouse Builder repository with this version of the product. |
|
Warehouse Builder Server Side (Runtime Platform Service) |
The server side environment requires Oracle 8.17 or Oracle9i Database Server Release 1 or 2. Prior to installing, refer to Appendix A, "Preparing an Oracle 8.1.7 or 9i Database" for recommended Oracle9i initialization parameters. Prior to installing, refer to Appendix A, "Preparing an Oracle 8.1.7 or 9i Database" for recommended Oracle9i initialization parameters. |
|
Warehouse Builder Design Browser Client |
The Warehouse Builder Design Browser client requires that you have a Web browser installed, and that your Oracle HTTP server is running on the database instance that hosts your design repository. |
|
Warehouse Builder Runtime Audit Browser Client |
The Warehouse Builder Runtime Audit Browser client requires that you have a Web browser installed. |
|
Warehouse Builder Design Browser if integrated with Oracle9i Application Server (Oracle9iAS) |
Integration of the Design Browser with Oracle9i Application Server is optional; if you choose to integrate it, the Warehouse Builder Design Browser requires Oracle9i Application Server Release 2 (9.0.2) or Release 2 (9.0.4). |
|
Warehouse Builder Runtime Audit Browser if integrated with Oracle9i Application Server (Oracle9iAS) |
Integration of the Runtime Audit Browser with Oracle9i Application Server is optional; if you choose to integrate it, the Warehouse Builder Runtime Audit Browser requires Oracle9i Application Server Release 2 (9.0.2) and Release 2 (9.0.4). |
A complete list of certified software for Oracle9i Warehouse Builder can be found on OracleMetaLink, which can be accessed at:
http://metalink.oracle.com
This section provides information about the coexistence of Oracle products in one ORACLE_HOME, and guidelines for installing multiple Oracle products on one machine. ORACLE_HOME is the root directory in which Oracle software is installed.
OWB_HOME\owb\j2ee\owbb, delete the owbb directory.
Before installing Oracle9i Warehouse Builder, review the Oracle9i Warehouse Builder Release Notes. The Oracle9i Warehouse Builder Release Notes are available on the Oracle9i Warehouse Builder CD-ROM. The latest Release Notes and Release Notes Addendum are also available on Oracle Technology Network at:
http://otn.oracle.com
The preinstallation tasks for Oracle9i Warehouse Builder are divided into the following parts:
PATH
CLASSPATH
LD_LIBRARY_PATH (UNIX Only)
SHLIB_PATH (HP-UX only)
Oracle Universal Installer and the Oracle9i Warehouse Builder Client are sensitive to the locale of the machine.
NLS_LANG.
Oracle Universal Installer and Oracle9i Warehouse Builder Client will display the installer user interface in the appropriate language as specified in the current locale. Be sure to set the locale before starting the installer.
The tasks in this section are required on UNIX platforms only.
To prevent a conflict between the software in an existing ORACLE_HOME and the Oracle9i Warehouse Builder installation, you must remove all references to the existing ORACLE_HOME in your environment. You must then set the ORACLE_HOME environment variable.
To prevent conflicts with other ORACLE_HOMEs, edit the following environment variables so they do not use the existing ORACLE_HOME value:
To set the ORACLE_HOME environment variable:
Use the following command (full_path is the path into which Oracle9i Warehouse Builder will be installed):
prompt> setenv ORACLE_HOME full_path
prompt> export ORACLE_HOME=full_path
prompt> ORACLE_HOME=full_path; export ORACLE_HOME
Setting the DISPLAY environment variable enables you to run the Oracle Universal Installer remotely from a local work station.
On the system where you run the Oracle Universal Installer, set DISPLAY to the system name or IP address of your local workstation.
If you get an Xlib error similar to "Failed to connect to server", "Connection refused by server", or "Can't open display" when starting the installer, then run the commands on your local workstations as listed in Table 1-9.
During installation, Oracle Universal Installer uses a temporary directory for swap space. This directory must meet the environment requirements listed in Table 1-2 before you install Oracle9i Warehouse Builder. The installation may fail if you do not have sufficient space. The installer checks for the TMP environment variable to locate the temporary directory. If this environment variable does not exist, then the installer uses the /tmp directory.
| Shell Types | Command |
|---|---|
|
C Shell |
|
|
Bourne Shell |
|
|
Korn Shell |
|
The tasks in this section are required on UNIX platforms only.
Use the utility provided on your operating system to create a group named oinstall. For example:
admintool or groupadd utility.
SAM utility.
YaST2 utility.
smit utility.
For more information on these utilities, refer to your operating environment documentation.
The oinstall group will own Oracle Universal Installer's oraInventory directory. The oracle user account that runs the installation must have the oinstall group as its primary group.
The oracle account is the UNIX account that owns Oracle software for your system. You must run Oracle Universal Installer from this account.
Create an oracle account with the properties listed in Table 1-11.
Use the oracle account only for installing and maintaining Oracle software. Never use it for purposes unrelated to the Oracle Universal Installer. Do not use root as the oracle account.
Oracle Universal Installer guides you through the installation screens. Depending on the operating environment and install option selected, you will require the information listed in Table 1-12.
| Item | Installation Type | Example |
|---|---|---|
|
ORACLE_HOME name and path for Oracle9i Warehouse Builder (See "Coexistence: ORACLE_HOME Considerations" for more details.) |
All (Windows and UNIX) |
|
|
UNIX group name |
All (UNIX only) |
|
Oracle9i Warehouse Builder uses Oracle Universal Installer to install components and to configure environment variables. The installer guides you through each step of the installation process.
The installer includes features that perform the following tasks:
The installer creates the Inventory or oraInventory directory the first time it is run on your machine. The inventory directory keeps a record of the products that the installer installs on your machine as well as other installation information. If you have previously installed Oracle products, then you may already have an inventory directory.
\Program Files\Oracle\Inventory.
oraInventory is defined in /var/opt/oracle/oraInst.loc.
oraInventory is defined in /etc/oraInst.loc.
oraInventory is defined in /etc/oraInst.loc.
Inventory_location\logs\installActionsDATE_TIME.log (Windows) or oraInventory_location/logs/installActionsDATE_TIME.log (UNIX). Log file names of installation sessions have the date and time appended to the names.
oraInventory directory. If another group attempts to run the installer, then they must have permission to write to the oraInventory directory. If they do not have permission, then the installation fails.
Follow these instructions to launch Oracle Universal Installer, which installs Oracle9i Warehouse Builder.
setup.exe in the root directory of the CD-ROM. Start the installer by launching the setup.exe program.
Proceed to Chapter 2, "Installing Oracle9i Warehouse Builder Components" for further instructions.
For operating environments that do not support automatic mounting of CD-ROMs, the Oracle9i Warehouse Builder installation CD-ROMs must be mounted manually. You must have root privileges to mount or unmount a CD-ROM. Be sure to unmount a CD-ROM before removing it from the drive.
The Oracle9i Warehouse Builder installation CD-ROM is in RockRidge format.
Please read the appropriate section for your platform:
If you are using the Solaris Volume Management software (installed by default with the Solaris operating environment), then the CD-ROM is mounted automatically to cdrom/Disk1 when you insert it in the disk drive.
If you are not using the Solaris Volume Management software, then you must mount the CD-ROM manually.
To mount the CD-ROM manually on Solaris:
root user.
prompt> mkdir mount_point
prompt> mount options device_name mount_point
The following example mounts the CD-ROM manually on /cdrom, without using the Solaris Volume Management software. Execute the following commands as the root user.
prompt> mkdir /cdrom prompt> mount -r -F hsfs device_name /cdrom
root user.
Follow these instructions to mount the CD-ROM on HP-UX.
To mount the CD-ROM manually on HP-UX:device_file:
prompt> ioscan -fun -C disk
/etc/pfs_fstab file for your CD-ROM device, you must add one. As the root user, use a system editor to add a line to the /etc/pfs_fstab file following this format:
device_file mount_point filesystem_type translation_method
In the preceding format, the first entry is the CD-ROM device, the second entry is the mount point, and the third entry indicates that the CD-ROM to be mounted is in ISO9660 format with Rockridge extensions. For example, if a CD-ROM device has the path /dev/dsk/c4t2d0, you would enter the following:
/dev/dsk/c4t2d0 /SD_CDROM pfs-rrip xlat=unix 1 0
root user.
prompt> nohup /usr/sbin/pfs_mountd & prompt> nohup /usr/sbin/pfsd &
prompt> /usr/sbin/pfs_mount /SD_CDROM
root user.
If you are using auto mounting software, the CD-ROM is mounted automatically to the directory specified in your auto mount configuration when you insert Disk 1 into the CD-ROM drive.
If you are not using auto mounting software, then you must mount the CD-ROM manually.
To mount the CD-ROM manually:
root user.
prompt> mkdir mount_point
prompt> mount options device_name mount_point
The following example mounts the CD-ROM manually on /cdrom, without using the Linux auto mounting software. Execute the following commands as the root user.
prompt> mkdir /cdrom prompt> mount -t iso9660 device_name /cdrom
root user.
Mount disk 1 to begin the installation. Mount the subsequent disk or disks when prompted to do so. Follow these steps to mount the Oracle9i CD-ROM manually.
To mount the CD-ROM manually:
$ su root
# mkdir cdrom_mount_point_directory
device_name:
# lsdev -Cc cdrom
The output should be similar to the following:
cd0 Available 10-60-00-4, 0 SCSI Multimedia CD-ROM Drive
# mount optionsdevice_namecdrom_mount_point_directory# exit
Example 1-1 shows how to mount the AIX CD-ROM manually.
$ su root # mkdir /cdrom # mount -rv cdrfs /dev/cd0 /cdrom # exit
In the preceding output, /dev/cd0 is the CD-ROM device.
After mounting the installation CD-ROM, you can run Oracle Universal Installer from the CD-ROM. Do not run the Installer while the CD-ROM directory is the current directory or you will be unable to unmount the next CD-ROM when prompted to do so.
To run Oracle Universal Installer from the CD-ROM:oracle user.
mount_point/runInstaller
This launches Oracle Universal Installer, through which you can install Oracle9i Warehouse Builder. Proceed to Chapter 2, "Installing Oracle9i Warehouse Builder Components" for further instructions.
|
|
![]() Copyright © 1996, 2003 Oracle Corporation. All Rights Reserved. |
|