StarQuest Technical Documents

Linux Prerequisites for StarSQL & StarLicense

Last Update:29 June 2017
Product: StarSQL
Version: 6.2
Article ID: SQV00SQ065

Abstract

When StarSQL and StarLicense are deployed to a different environment than the one in which they were built (e.g. a later distribution of Linux), it is sometimes necessary to install prerequsite packages.

This is especially true for installing 32-bit packages in a 64-bit environment, as the 32-bit runtime libraries are not installed by default in most recent Linux distributions.

The techniques described in this technical document apply to RPM-based Linux distributions such as Red Hat, CentOS, SUSE, and Oracle. Similar techniques are available on Debian & Ubuntu distributions.

These techniques can also be used to identify missing dependencies for 64-bit packages.

These procedures were tested on 64-bit versions of CentOS 6.9 and CentOS 7.2. Note that the version numbers included in package names may differ.

Solution

StarSQL

StarSQL is available in both 64-bit and 32-bit versions; installing the 32-bit version may be desirable if the ODBC application is also 32-bit. Typically, there are no problems installing the 64-bit version of StarSQL, so this technical document highlights issues installing 32-bit software.

To identify missing packages, locate the StarSQL RPM in the installation directory and run a command like this:

# rpm -i starsql-6.28-1.i386.rpm

This will either install the product or list missing libraries. If the installation succeeds, then all prerequisites are present; however, the installation of StarSQL is incomplete since the post-install procedure was not run; at this point, you should remove the product and reinstall using the setup shell script:

# rpm -e starsql
# ./setup

But in most situations there will be missing libraries. You can ignore libodbc.so.1 and libodbcinst.so.1, since the recommended version of unixODBC is included in the StarSQL distribution.

The missing libraries can be divided into two groups:

  • Those needed for 32-bit runtime support (C++ runtimes, etc)
  • Those needed for GUI support (QT3, X Windows, etc)

To install the missing 32-bit support, run the following:

# yum install libstdc++.i686

This will also include the dependencies glibc.i686, libgcc.i686, nss-softokn-freebl.

After installing the 32-bit runtimes, running rpm -i starsql-6.28-1.i386.rpm should now display only the dependencies for QT3 and X-Windows (and ODBC), and you should be able to run the non-GUI components of StarSQL.

To add GUI support (e.g. to run ODBCConfig and the supplied samples odbctest, DataManager, and DataManagerII), run the following:

Use this command to determine which Linux package contains the missing library libqt-mt.so.3:
# yum provides libqt-mt.so.3

Run this command to install that package and its dependencies:
# yum install qt3-3.3.8b-30.el6.i686

Other methods of identifying missing libraries are:

  • Run the product - you should receive an error listing the missing libraries
  • Use the ldd command and note which libraries are listed as Not Found.

After determining the name of the missing library, use
# yum provides <library-name>
to determine the name of the installer package.

StarLicense

StarLicense Server is currently only available as a 32-bit package

Run the following to install the 32-bit C and C++ runtime libraries:

# yum install libstdc++.i686

This will also include the dependencies glibc.i686, libgcc.i686, nss-softokn-freebl.

You can use the following to verify that dependencies are met (install the product with RPM, remove it, and reinstall with the setup script):

# rpm -i starlicense-1.33-1.i386.rpm
(this will either display missing libraries, or succeed)
# rpm -e starlicense
# ./setup

 

 


DISCLAIMER

The information in technical documents comes without any warranty or applicability for a specific purpose. The author(s) or distributor(s) will not accept responsibility for any damage incurred directly or indirectly through use of the information contained in these documents. The instructions may need to be modified to be appropriate for the hardware and software that has been installed and configured within a particular organization.  The information in technical documents should be considered only as an example and may include information from various sources, including IBM, Microsoft, and other organizations.