Installing Optim High Performance Unload on UNIX and Linux systems

You can install Optim™ High Performance Unload on UNIX™ and Linux™ systems using the console mode.

Procedure

  1. Insert the product CD into the CD drive of the computer where you want to install Optim High Performance Unload.
  2. Log into the system as a user with root authority.
  3. Mount the CD on a suitable mount point (for example, /mnt/cdrom).
  4. Change to the directory that corresponds to the platform under the CD mount point.
    For example, for AIX® systems, enter: cd /mnt/cdrom/aix
  5. Copy or move the compressed Optim High Performance Unload tar file (xxx.tar.gz) into a directory with sufficient free space.
  6. Uncompress and untar the file.
    For example:
    gunzip -c xxxxx.tar.gz | tar -xvf -
    After the file is untarred, an additional HPU6500 subdirectory will be created.
  7. Change to the HPU6500 subdirectory.
  8. If there is already a "Try and Buy" version installed, run either the ./install_hpu.sh -a command or the ./install_hpu.sh -d <hpu_install_directory> -a command as a root user. If you omit the -a the install will end in error. If there is no "Try and Buy" version installed, run either the ./install_hpu.sh command or the ./install_hpu.sh -d <hpu_install_directory> command as a root user.
    If you start the installer without any parameters, Optim High Performance Unload will be installed in the /opt/ibm/HPU/V12.1 directory on Linux systems, or in the /opt/IBM/HPU/V12.1 directory on other UNIX systems. The -a option allows to upgrade to a full license of the product without having to uninstall an already existing Try and Buy version and without potentially losing any product configuration that would have been made on this Try and Buy installation.
  9. Follow the instructions in the prompts.
    The install process will automatically install all of the following components:
    Optim High Performance Unload Base
    This component provides the base Optim High Performance Unload functionality.
    Optim High Performance Unload Network Support
    The executing Optim High Performance Unload code must be on the same physical machine as the Db2® data because Optim High Performance Unload reads the Db2 container files directly. In a partitioned environment, Optim High Performance Unload uses its network component or daemon to execute the Optim High Performance Unload code on remote systems. The Optim High Performance Unload daemon is also needed when running Optim High Performance Unload through its stored procedure.

    The Optim High Performance Unload daemon installs and sets itself up to be started by the "Super Server" inetd or xinetd. One of these services must be installed and running on your system during the installation or the installation will fail.

    Db2 Stored Procedure
    This component installs the function that allows you to run Optim High Performance Unload as a stored procedure.
    Attention: If you choose this option, the Optim High Performance Unload installation process will install all of the files necessary to configure Optim High Performance Unload as a Db2 stored procedure. Refer to Configuring Optim High Performance Unload as a Db2 stored procedure on Linux and UNIX platforms for configuration instructions.

    In cases where the executing Optim High Performance Unload code is started by the daemon, the locale that the daemon uses will be the default locale for that unload.

What to do next

Before running Optim High Performance Unload for the first time, the DBA should configure it. You might make entries for the default instance or the default database, especially if you have used previous versions of Optim High Performance Unload since in some prior versions the default instance and the default database were set during the installation process.
You can also change the ownership of the cfg subdirectory (under the installation directory) and all the files contained within it so that changes can be made by the DBA without the assistance of the system support group. For example, to change the ownerid to mydba and the group to dbagroup, use the following command:
chown -R mydba:dbagroup directoryname/cfg