Installing on Linux/UNIX Clients

The topic describes how to install the UNIX client packages on 32-bit and 64-bit operating system workstations.

About this task

If you are installing the clients on 64-bit operating systems, there are some additional steps to install a second, 64-bit client package. The Netezza clients are 32-bit operating system executables and they require 32-bit libraries that are not provided with the clients. If the libraries are not already installed on your system, you must obtain and install the libraries by using your operating system update process.

Procedure

  1. Obtain the nz-platformclient-version.archive) client package from the IBM Fix Central site and download it to the client system. Use or create a new, empty directory to reduce any confusion with other files or directories.
    There are several client packages available for different common operating system types, as described in Client software packages. Make sure that you obtain the correct client package. These instructions use the Linux client package as an example of the procedure.
  2. Log in to the workstation as the root user or a superuser account.
  3. Change to the directory where you saved the client package, then uncompress and extract the contents.

    For the Linux client, use the gunzip command to uncompress the client package, then you use a command such as tar xzf nz-linuxclient-version.tar.gz to extract the package. To extract the other UNIX packages, such as AIX®, you might need to run other commands, such as uncompress to uncompress the archive.

    The unpack process for the Linux package creates a linux directory, a linux64 directory, a webadmin directory, and a datadirect.package.tar.z file. Ignore the webadmin directory, which contains the Web Admin interface client.
  4. Change to the linux directory and run the unpack command to install the 32-bit CLI files: ./unpack.
    Note: On an HP-UX 11i client, /bin/sh might not be available. You can use the command form sh ./unpack to unpack the client.
    The unpack command checks the client system to ensure that it supports the CLI package and prompts you for an installation location. The default is /usr/local/nz for Linux®, but you can install the CLI tools to any location on the client. The program prompts you to create the directory if it does not already exist. Sample command output follows:
    ------------------------------------------------------------------
    IBM IPS -- NPS Linux Client 11.2.0.0
    (C) Copyright IBM Corp. 2002, 2020 All Rights Reserved.
    ------------------------------------------------------------------
    Validating package checksum ... ok
    
    Where should the NPS Linux Client be unpacked? [/usr/local/nz]
    Directory '/usr/local/nz' does not exist; create it (y/n)? [y] Enter
    0%             25%          50%          75%             100%
    |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
    Unpacking complete.
    
  5. If your client has a 64-bt operating system, change to the linux64 directory and run the unpack command to install the 64-bit CLI files:./unpack.
    The unpack command prompts you for an installation location. The default is /usr/local/nz for Linux, but you should use the same location that you used for the 32-bit CLI files in the previous step. Sample command output follows:
    ------------------------------------------------------------------
    IBM IPS -- NPS Linux Client 11.2.0.0
    (C) Copyright IBM Corp. 2002, 2020 All Rights Reserved.
    ------------------------------------------------------------------
    Validating package checksum ... ok
    
    Where should the NPS Linux Client be unpacked? [/usr/local/nz]
    
    Installing in an existing directory. Changing permissions to
    overwrite existing files...
    0%             25%          50%          75%             100%
    |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
    Unpacking complete.
    

Results

The client installation steps are complete, and the Netezza Performance Server CLI commands are installed to your specified destination directory. The Netezza Performance Server commands are located in the bin directory where you unpacked the Netezza Performance Server clients. If you are using a 64-bit operating system on your workstation, note that there is a 64-bit nzodbcsql command in the bin64 directory for testing the SQL command connections.

What to do next

Test to make sure that you can run the client commands. Change to the bin subdirectory of the client installation directory (for example, /usr/local/nz/bin). Run a sample command such as the nzds command to verify that the command succeeds or to identify any errors.

./nzds -host nzhost -u user -pw password

The command displays a list of the data slices on the target Netezza Performance Server system. If the command runs without error, your client system has the required libraries and packages to support the Performance Server clients. If the command fails with a library or other error, the client may require some additional libraries or shared objects.

For example, on a Red Hat Enterprise Linux 64-bit client system, you could see an error similar to the following:

[root@myrhsystem bin]# ./nzds
-bash: ./nzds: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory

For example, on a SUSE 10/11 64-bit client system, you could see an error similar to the following:

mylinux:/usr/local/nz/bin # ./nzds
./nzds: error while loading shared libraries: libssl.so.4: cannot open shared
object file: No such file or directory

mylinux:/usr/local/nz/bin # ldd nzds
linux-gate.so.1 => (0xffffe000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0xf76f1000)
libdl.so.2 => /lib/libdl.so.2 (0xf76ec000)
libssl.so.4 => not found
libcrypto.so.4 => not found
libm.so.6 => /lib/libm.so.6 (0xf76c4000)
libc.so.6 => /lib/libc.so.6 (0xf7582000)
/lib/ld-linux.so.2 (0xf773f000)

These errors indicate that the client is missing 32-bit library files that are required to run the Netezza Performance Server clients. Identify the packages that provide the library and obtain those packages. You may need assistance from your local workstation IT administrators to obtain the operating system packages for your workstation.

To identify and obtain the required Red Hat packages, you could use a process similar to the following.

  • Use the yum provides command and specify the file name to see which package provides the file that could not be found (ld-linux.so.2 in this example).
    yum provides ld-linux.so.2
    Loaded plugins: product-id, refresh-packagekit, security, subscription-manager
    This system is not registered to Red Hat Subscription Management. You can use
    subscription-manager to register.
    RHEL64 | 3.9 kB 00:00 ...
    glibc-2.12-1.107.el6.i686 : The GNU libc libraries
    Repo : RHEL64
    Matched from:
    Other : ld-linux.so.2

    In this example, the missing package is glibc-2.12-1.107.el6.i686.

  • In some cases, the Netezza Performance Server command could report an error for a missing libssl file. You can use the yum provides command to obtain more information about the packages that contain the library, and if any of the files already exist on your workstation.
    yum provides */libssl*
    Loaded plugins: product-id, refresh-packagekit, security, subscription-manager
    This system is not registered to Red Hat Subscription Management. You can use
    subscription-manager to register.
    nss-3.14.0.0-12.el6.x86_64 : Network Security Services
    Repo : RHEL64
    Matched from:
    Filename : /usr/lib64/libssl3.soopenssl-devel-1.0.0-27.el6.x86_64 : Files for
    : development of applications which will use OpenSSL
    Repo : RHEL64
    Matched from:
    Filename : /usr/lib64/pkgconfig/libssl.pc
    Filename : /usr/lib64/libssl.so

    To resolve the problem, you may need to obtain and install the package nss-3.14.0.0-12.el6.x86_64 or you might be able to create a symbolic link if the library already exists on your system. Use caution when creating symbolic links or changing the library files. You should consult with your IT department to ensure that you can obtain the needed packages, or that changes to the symbolic links will not impact the operation of other applications on your workstation.

Based on the missing libraries and packages, use the following steps to obtain the Red Hat packages.

  • Mount the Red Hat distribution DVD or ISO file to the client system. Insert the DVD into the DVD drive.
  • Open a terminal window and log in as root.
  • Run the following commands:
    [root@myrhsystem]# mkdir /mnt/cdrom
    [root@myrhsystem]# mount -o ro /dev/cdrom /mnt/cdrom
  • Create the text file server.repo in the /etc/yum.repos.d directory.
    Note: To use gedit, run the command: gedit /etc/yum.repos.d/server.repo and add the following text to the file where baseurl is the mount point and the RHEL distribution. In the example, the mounting point is cdrom and the RHEL distribution is Workstation but it could be a server or the ISO file.
    name=server
    baseurl=file:///mnt/cdrom/Workstation
    enabled=1
  • Run the command: yum clean all
  • Run the command to import related public keys: rpm --import /mnt/cdrom/*GPG*
  • Run the following command to install the required libraries: yum install <package-name> where <package-name> is the file that contains the libraries that you require for the Netezza Performance Server command operations.

To identify and obtain the required SUSE packages, you could use a process similar to the following.

  • Log in to the SUSE system as root or a superuser.
  • If the test Netezza Performance Server command failed with the error that libssl.so.4 or libcrypto.so.4 or both could not be found, you could be able to resolve the issue by adding a symbolic link to the missing file from the Netezza Performance Server client installation directory (for example, /usr/local/nz/lib). Use the ls /lib/libssl* command to list the available libraries in the standard OS directories. You could then create symbolic links to one of your existing libssl.so and libcrypto.so files by using commands similar to the following:
    mylinux:/usr/local/nz/lib # ln -s /usr/lib/libssl.so.0.9.8 /lib/libssl.so.4
    mylinux:/usr/local/nz/lib # ln -s /usr/lib/libcrypto.so.0.9.8 /lib/libcrypto.so.4
  • If you are missing other types of files or libraries, use the zypper wp command and specify the file name to see which package provides it. An example follows.
    zypper wp ld-linux.so.2
    Loading repository data...
    Reading installed packages...
    S | Name        | Type    | Version  | Arch   | Repository
    --+-------------+---------+----------+--------+---------------------------------
    i | glibc-32bit | package | 2.9-13.2 | x86_64 | SUSE-Linux-Enterprise-Desktop-11

    In this example, the missing package is glibc-32bit.

If the error indicates that you are missing other libraries or packages, use the following steps to obtain the SUSE packages.

  • Open a terminal window and log in as root.
  • Run the yast command to open the YaST interface.
  • One the YaST Control Center, select Software and go to the software repositories to configure and enable a DVD, a server, or an ISO file as a repository source. Select the appropriate source for your SUSE environment. Consult with your IT department about the policies for package updates in your environment.
  • On the Software tab, go to Software Management and search for the required package or library such as glibc-32bit in this example.
  • Click Accept to install the required package.
  • Exit YaST by clicking Quit.