DB2 OLAP Server Installation Guide

Installing DB2 OLAP Server on UNIX

The user under which you are installing DB2 OLAP Server must have both write and execute privileges in the directory where you are running the installation. If you install the DB2 OLAP Server as root, then other users might have difficulty accessing the server and updating the installation with IBM FixPaks, so it is recommended that you install under a user name other than "root."

Ensure that you have adequate disk space available on your system. Run df-k to check the percentage of space available on the mount where you are installing DB2 OLAP Server.

During the installation, you will be asked to enter the DB2 OLAP Server license edition and options that you purchased. This information is used to build a license key for DB2 OLAP Server and to enable the products for which you have licenses.

Installation steps for DB2 OLAP Server

1. Log on to the server with a user ID that will be the administrator of DB2 OLAP Server. Do not use root.
2. If you are installing on a Solaris operating system, set the locale to c. When you have finished installing, make sure the locale is still c when you start the server for the first time. Using the correct locale ensures that the administration user ID is configured correctly.
3. If your workstation has a CD-ROM drive, follow these steps:
   1. Insert the DB2 OLAP Server CD into your CD-ROM drive.
   2. Use the ls command to find setup.sh on the CD. The file name will be either uppercase or lowercase, depending on your operating system.
   3. Enter setup.sh to run the setup script from the DB2 OLAP Server CD.
4. If your workstation does not have a CD-ROM drive, you must create a temporary directory for use during the installation. To create a temporary directory, follow these steps:
   1. Use FTP, NFS, or any similar utility to copy the DB2 OLAP Server installation files into your temporary directory.
   2. Change to the temporary directory.
   3. Use the ls command to find setup.sh in the temporary operating system subdirectory. For example, look in /temp/aix for the AIX installation file. The file name will be either uppercase or lowercase, depending on your operating system.
   4. Enter setup.sh to run the setup script from the temporary directory.
5. If your operating system is not compatible with DB2 OLAP Server, you will receive a notification from the installation, which will then exit. If a multi-threaded environment is not detected, you will receive an error message.

To install DB2 OLAP Server:

1. Change to the directory where you want to install DB2 OLAP Server. This directory can be pre-existing, or a directory that will be created by the installation program. IBM strongly recommends that you install DB2 OLAP Server and its features into a new separate directory; do not install into directory in which a product other than DB2 OLAP Server and its features has been installed.
2. If you have a current DB2 OLAP Server license in another directory that you want to use for the current installation, enter that directory during installation for licensing reference.
3. In the License Agreement window, enter or select the following information::
   1. Select the number that corresponds with the language in which you would like to read the IBM license.
   2. Press Enter to view the license for approval.
   3. Press 1 to accept the agreement, 2 to decline it, or 99 to return to the previous screen.

      The IBM License Agreement Utility will then complete the licensing. The installation will continue to the next panel if the license was accepted, or exit the installation if the license was declined.

4. Select the license edition that you purchased.
5. Select the license options that you purchased, including the number of users licensed.
6. Select the products that you want to install.
7. After verifying that the summary is correct, select Continue.
8. Select Install to run the installation.

   The installation directory includes a log file (olapinst.log) located in <ARBORPATH>/install, and a response file (olapisnt.rsp) that can be used for silent or unattended installations. The log file includes the license information and a list of the installed products. Additionally, it includes any installation errors if they occurred.