Installing the client tools software (UNIX and Linux)

You can install the UNIX and Linux clients on 32-bit and 64-bit operating system workstations.

Before you begin

Obtain the applicable client media. See Client software packages.

About this task

The Netezza Performance Server clients are 32-bit operating system executable files, and they require 32-bit operating system 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.

If you are installing the clients on Linux 64-bit operating systems, there is an additional step to install a second, 64-bit client package.

Procedure

Log in to the workstation as the root user or a superuser.
Perform one of the actions in the following list. In doing so, make sure that you use the client release that matches the Netezza Performance Server software release of your Netezza Performance Server system. Do not use Netezza Performance Server clients to manage Netezza Performance Server systems that use a different Netezza Performance Server release.
- Insert the IBM® Netezza Client Components DVD into the DVD drive of your client system.
- If you downloaded the client package to a directory on your client system, change to that directory and extract the package.
Install the client by issuing the ./unpack command.
On Linux systems, if you are installing the nz-linuxclient-version-tar.gz package, issue the ./unpack command from the linux directory.

On an HP-UX 11i client, /bin/sh might not be available. To unpack the client, you can use the command form sh ./unpack.
The unpack command checks the client system to ensure that it supports the CLI package and prompts you for an installation location. The default for Linux® operating systems is the /usr/local/nz directory, but you can install the CLI tools in any location on the client. The program prompts you to create the directory if it does not exist. Sample command output follows:
```
------------------------------------------------------------------
IBM Netezza -- NPS Linux Client 7.2.1.1
(C) Copyright IBM Corp. 2002, 2015 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.
```

If your client has a 64-bit Linux operating system, in the linux64 directory, install the 64-bit CLI files by issuing the ./unpack command.

The unpack command prompts you for an installation location. The default is the /usr/local/nz directory. Use the same location that you used for the 32-bit CLI files in the previous step. Sample command output follows:

------------------------------------------------------------------
IBM Netezza -- NPS Linux Client 7.2.1.1
(C) Copyright IBM Corp. 2002, 2015 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 is installed, and the Netezza Performance Server CLI commands are installed in your specified destination directory. The NPS commands are located in the bin directory into which you unpacked the NPS clients. If you are using a 64-bit operating system on your workstation, you can use the 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 following one to check whether 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 NPS system. If the command runs without error, your client system has the required libraries and packages to support the Netezza® clients. If the command fails with a library or other error, the client might require some additional libraries or shared objects.

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

[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 might see an error that is similar to the following one:

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 the operating system 32-bit library files that are required to run the NPS clients. Identify and obtain the packages that provide the library. You might 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 that is similar to the one in the following list:

To see which package provides the file that could not be found, issue the yum provides command, specifying the name of the file that could not be found. In the following example, ld-linux.so.2 is the file that could not be found, and the missing package is glibc-2.12-1.107.el6.i686:

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

The NPS command might report an error for a missing libssl file. To obtain more information about the packages that contain the library and see whether any of the files already exist on your workstation, you can issue the yum provides command. An example follows:
```
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 in the previous example, you might need to obtain and install the nss-3.14.0.0-12.el6.x86_64 package, 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:
1. Mount the Red Hat distribution DVD or ISO file to the client system. Insert the DVD into the DVD drive.
2. Open a terminal window and log in as root.
3. Issue the following commands:
```
[root@system_name]# mkdir /mnt/cdrom
[root@system_name]# mount -o ro /dev/cdrom /mnt/cdrom
```
4. In the /etc/yum.repos.d directory, create the server.repo text file. For example, to use gedit, issue the following command:
```
gedit /etc/yum.repos.d/server.repo
```
5. Add name=server, baseurl, and enabled=1 entries to the file, where baseurl specifies the mount point and the RHEL distribution. In the following example, the mount 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
```
6. Issue the following command:
```
yum clean all
```
7. Import related public keys by issuing the following command:
```
rpm --import /mnt/cdrom/*GPG*
```
8. Install the required libraries by issuing the following command:
```
yum install <package_name>
```
  where <package_name> is the file that contains the libraries that you require for the NPS command operations.

To identify and obtain the required SUSE packages, you could use a process that is similar to the following one:

Log in to the SUSE system as root or a superuser.
Use the applicable approach:
- If the test NPS command failed with the error that the libssl.so.4 file, the libcrypto.so.4 file, or both files could not be found, try to resolve the issue by adding a symbolic link to the missing file from the NPS client installation directory (for example, /usr/local/nz/lib):
  1. List the available libraries in the standard operating system directories by issuing the ls /lib/libssl* command.
  2. Create symbolic links to one of your existing libssl.so and libcrypto.so files by issuing commands similar to the following one:
```
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, take the following steps:
  1. Issue the zypper wp command, specifying the file name to see which package provides the file or library. 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.
  2. Obtain the SUSE packages as follows:
    1. Open a terminal window and log in as root.
    2. Open the YaST interface by issuing the yast command.
    3. In the YaST Control Center, click 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.
    4. On the Software tab, click Software Management and search for the required package or library, such as glibc-32bit in the previous example.
    5. Install the required package by click Accept.
    6. Exit YaST by clicking Quit.