Informix
Informix
on Linux
Version 7.3
December 1998
Part No. 000-5274
Published by INFORMIX Press Informix Corporation
4100 Bohannon Drive
Menlo Park, CA 94025-1032
1998 Informix Corporation. All rights reserved. The following are trademarks of Informix Corporation or its
affiliates:
Answers OnLineTM; CBT StoreTM; C-ISAM; Client SDKTM; ContentBaseTM; Cyber PlanetTM; DataBlade; Data
DirectorTM; Decision FrontierTM; Dynamic Scalable ArchitectureTM; Dynamic ServerTM; Dynamic ServerTM,
Developer EditionTM; Dynamic ServerTM with Advanced Decision Support OptionTM; Dynamic ServerTM with
Extended Parallel OptionTM; Dynamic ServerTM with MetaCube ROLAP Option; Dynamic ServerTM with
Universal Data OptionTM; Dynamic ServerTM with Web Integration OptionTM; Dynamic ServerTM, Workgroup
EditionTM; FastStartTM; 4GL for ToolBusTM; If you can imagine it, you can manage itSM; Illustra; INFORMIX;
Informix Data Warehouse Solutions... Turning Data Into Business AdvantageTM; INFORMIX-Enterprise
Gateway with DRDA; Informix Enterprise MerchantTM; INFORMIX-4GL; Informix-JWorksTM; InformixLink;
Informix Session ProxyTM; InfoShelfTM; InterforumTM; I-SPYTM; MediazationTM; MetaCube; NewEraTM;
ON-BarTM; OnLine Dynamic ServerTM; OnLine for NetWare; OnLine/Secure Dynamic ServerTM; OpenCase;
ORCATM; Regency Support; Solution Design LabsSM; Solution Design ProgramSM; SuperView; Universal
Database ComponentsTM; Universal Web ConnectTM; ViewPoint; VisionaryTM; Web Integration SuiteTM. The
Informix logo is registered with the United States Patent and Trademark Office. The DataBlade logo is
registered with the United States Patent and Trademark Office.
Documentation Team: Twila Booth, Abby Knott, Barbara Nomiyama, Eileen Wollam
Software and documentation acquired by or for the US Government are provided with rights as follows:
(1) if for civilian agency use, with rights as restricted by vendor’s standard license, as prescribed in FAR 12.212;
(2) if for Dept. of Defense use, with rights as restricted by vendor’s standard license, unless superseded by a
negotiated vendor license, as prescribed in DFARS 227.7202. Any whole or partial reproduction of software or
documentation marked with this legend must reproduce this legend.
Table of Contents
Index
iv Installation Guide for Informix Products on Linux
About This Manual
This manual contains instructions for how to install Informix Dynamic
Server, Linux Edition Suite on computers that run the Linux operating
system. Keep it with your Informix software documentation for easy
reference.
Types of Users
This manual is written for database administrators who install Informix
products. This manual assumes that you are familiar with the operating
procedures of your computer and with your operating system and that you
are authorized to log into your system as root.
Software Dependencies
This manual is written with the assumption that the Red Hat Package
Manager (RPM) is installed on your Linux computer. Informix provides most
of the products in Informix Dynamic Server, Linux Edition Suite in RPM-
package format.
Installation Packages
The information in this manual describes the basic installation procedures in
a Linux environment for the following Informix products:
■ Informix Dynamic Server, Linux Edition, Version 7.3
■ INFORMIX-Connect, Version 2.1.
■ INFORMIX-Client Software Developer’s Kit, Version 2.1
The Client SDK package file contains the following client products:
■ INFORMIX-CLI
■ INFORMIX-ESQL/C
■ INFORMIX-GLS
■ INFORMIX-Object Interface for C++
If you want to install INFORMIX-Driver for JDBC, you must obtain this
product separately.
For more information about the Client SDK products, refer to the Getting
Started manual.
You need the serial number and key to install and activate your Informix
products. Use the information in Figure 1 to locate the serial number and key.
Figure 1
Obtaining the Serial Number and Key
Download from the Record the serial number and key that display when you
Internet download the product.
The following table describes the general steps in installation and where to
find the information you need for each step.
If necessary, upgrade the Linux operating The Informix Linux Web page,
environment with a patch supplied by your [Link]/linux.
Linux distributor.
You do not have to install the products in a specific order. Beginning with
Version 7.3, you can install Dynamic Server first or the Client SDK first.
If you install more than one Informix product, complete all installation
procedures for one product before you start to install the next product. Do
not load the files from another Informix product onto your computer until
you complete the current installation.
Version Compatibility
This section explains the compatibility between different versions of
Informix database servers and client products.
Informix client products that precede Version 2.1 are compatible with
Dynamic Server, Version 7.3.
Version 2.1 client products are compatible with the following database
servers:
■ Informix Dynamic Server, Version 7.x
■ Informix Dynamic Server with Advanced Decision Support and
Extended Parallel Options, Version 8.1x
■ Informix Dynamic Server with Universal Data Option, Version 9.1x
■ Informix Dynamic Server, Developer Edition, Version 7.x
■ Informix Dynamic Server, Workgroup Edition, Version 7.x
■ INFORMIX-SE, Version 7.x
To use database servers earlier than Version 7.3 with Client SDK, Version 2.1,
replace the shared ESQL/C libraries at the appropriate time in the installation
process, as “Running the Installation Scripts” on page 13 describes.
To find out if you need to apply patches, refer to the Informix Linux Web page
at [Link]/linux. The Linux Web page contains links to a variety
of current information about Informix products for Linux.
If any Informix product is currently installed, skip this section and go directly
to “Preparing the Package-Manager Environment” on page 8.
The user informix is the database equivalent of the Linux root account,
which means that anyone logged in as informix has complete access to any
Informix products and databases. Make sure that you keep the password for
the user informix confidential.
The default Linux location for Informix products is /opt/informix. To use the
default, create an /opt/informix directory.
You can use a different location than the default path. For example, you can
preserve Version 7.2 in /opt/informix and create an /opt/informix73 directory
for Version 7.3.
Shell Commands
For more information about the Informix environment variables, see the
Informix Guide to SQL: Reference.
■ the difference between Informix package files for the RPM and other
types of RPM package files.
■ the distinction between a package file and a binary package.
A package file contains a software package, such as the database server, and a
preamble that describes the package. The binary package includes an
installation utility, sample configuration files, and executable libraries within
a compressed archive.
Important: The rpm package-manager utility does not install Informix software. The
package manager transfers pre-installation files to the appropriate location on your
hard drive. Each package includes its own installation utility. You can load all the
Informix packages with rpm at this time, before you run the installation utility for
any one of the products.
The name of a binary package file or package name contains the following
variable information:
Command Purpose
rpm -qp * Queries the names of packages in the binary package files
that reside in the current directory
rpm -qpi *.rpm Queries detailed information about the binary package files
(with the filename extension .rpm) that reside in the current
directory
rpm -qa Queries the names of the installed packages that are
maintained in the RPM database
rpm -iv ids* Loads the Dynamic Server package under /opt/informix
rpm -iv *.rpm Loads the Dynamic Server, Client SDK, and Connect
packages under /opt/informix
INFORMIXDIR=/opt/informix/LE Loads all the Informix packages under the directory that
export INFORMIXDIR INFORMIXDIR is set to, in this example /opt/informix/LE
rpm -iv --prefix $INFORMIXDIR *.rpm
Uninstalling a Package
When you use the rpm -e command, Informix product packages perform the
following actions:
■ Check that user root executes the command and stops if you use any
other login identity, including informix
■ Delete the package entry from the RPM database
■ Delete the files and subdirectories that the previous rpm -i command
created on the hard drive
You can uninstall an Informix package after you extract it, before or after you
run the installation scripts that “Running the Installation Scripts” on page 13
describes. However, the rpm -e command does not remove any files or
directories that are created by the installation scripts.
The example in Figure 2 queries the RPM database for Dynamic Server, and
then uninstalls the database server product.
Figure 2
$ rpm -qi ids Querying and
Version : 7.30.UC5 Removing a
Release : 1
Package
…
The number at the end of each filename indicates the product version
number for that file (for example, SERVERS_7.3 or DBACCDOC_7.3).
When you use any Informix manual, also refer to the documentation-notes,
release-notes, and machine-notes files that are referenced in that manual.
References to these files appear in the introduction of each manual.
The following table lists some of the on-line files for Dynamic Server and the
Client SDK.
INFORMIX-Connect ./installconn
Option Meaning
If you do not supply one of these options, the script asks you to
specify the database server with which you are installing Connect.
The -u argument pertains to client applications that run with
Informix database servers, Version 7.1x or Version 7.2x. When you
use the -u argument, the installation script overwrites Version 7.x
shared library files for ESQL/C. (As of Version 7.3, Dynamic Server
no longer includes shared ESQL/C library files.)
The -u argument enables Version 2.1 client applications to work with
INFORMIX-SE on Linux. If you use the -u argument, recompile and
relink Version 7.x client applications because Version 2.1 shared
libraries are not backward compatible with Version 7.x shared
ESQL/C libraries. For more information, refer to the machine notes
for Client SDK, Version 2.1.
3. Press RETURN to continue the installation procedure.
The following prompt appears:
Enter your serial number (for example, INF#X999999) >
4. Enter the 11-character License S/N from your serial-number
keycard.
The License S/N consists of three uppercase letters, followed by a
pound sign (#), followed by one uppercase letter and six digits.
After you press RETURN, the script prompts you to enter your Key.
5. Enter the six-letter Key from your serial-number keycard.
After you press RETURN, the script displays a message about the
license agreement with Informix. If your software is licensed for use
by an unlimited number of simultaneous users, the script displays a
message to that effect.
Shell Commands
Bourne LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$INFORMIXDIR/java/lib/
Again shell export LD_LIBRARY_PATH
(bash)
For more information, use a Web browser and the following URL to access the
on-line documentation for INFORMIX-Driver for JDBC:
file:$INFORMIXDIR/lib/java/doc/[Link]
To enable the browser to locate the [Link] file, specify the absolute
pathname of the $INFORMIXDIR directory rather than the environment
variable $INFORMIXDIR. The following example, shows the default location:
file:/opt/informix/lib/java/doc/[Link]
Important: Before you can connect a client application to a database server, confirm
that you have configured your database server environment.
A distorted display indicates that these environment variables are not set
correctly for your terminal. To check for distortion, run a text editor program,
such as vi.
If you need to modify the termcap file, make the modifications in a copy of
the file and reference the modified file with the TERMCAP environment
variable.
Each installation script installs the following GLS locale and code-set
conversion files in the $INFORMIXDIR/gls directory on your hard disk:
Package-Manager Failures
The problems in this section can occur while you use the rpm utility to load
or unload an Informix package:
■ Problem. The command displays one of the following messages:
ERROR: You must be root to install product.
ERROR: You must be root to uninstall product.
Solution. Check that you are logged in as root.
Install-Script Failures
The problems in this section can occur while you attempt to run the
installconn, installclientsdk, or installserver script:
■ Problem. After you enter the six-letter key, the script displays the
following message:
etc/brand: invalid serial number and/or key.
** Verify serial number and key values. **
** Restart installation procedure. **
** Please type carefully. **
Solution. This message usually results from a typing error in the serial
number or key. Check the serial number and key, then enter them
again. To locate the serial number and key, refer to Figure 1
on page 2.
If the serial number and key are correct, set the erase character. An
incorrect setting can cause the installation script to misinterpret a
keystroke in a valid serial number or key as a backspace. For
example, the installation script might interpret a pound sign (#) as an
erase or backspace.
To set the erase character, log in as root and then enter the following
command:
stty erase CTRL-h
CTRL-h looks like ^H on the screen.
After you execute the stty command, repeat the steps in “Running
the Installation Scripts” on page 13 and all subsequent steps. If this
problem occurs again, repeat the steps in “Extracting a Binary
Package from a Package File” on page 9 and all subsequent steps.
■ Problem. After you enter the six-letter key, the script displays the
following message:
Unknown message number 32766.
Solution. This problem occurs when you do not set INFORMIXDIR
before you run the installation script. Set INFORMIXDIR and repeat
the steps in “Running the Installation Scripts” on page 13 and all
subsequent steps.
■ Problem. When you try to list all databases, the list is incomplete.
Solution. Make sure that the DBPATH environment variable contains
the names of all other database servers not referenced by the
INFORMIXSERVER environment variable.
■ Problem. When you start a client product, the screen display is
distorted.
Solution. This problem occurs when the TERM or TERMCAP
environment variables are set incorrectly. For information about how
to set these variables, refer to “Setting the Terminal Characteristics”
on page 16 and to the Informix Guide to SQL: Reference.
■ Problem. Unusual problems occur, such as networking problems or
unexplainable crashes.
Solution. This problem occurs when your operating system needs a
patch. For patch information, see the machine-notes file in
$INFORMIXDIR/release/en_US/0333.
Index
Index
B E
Bourne Again shell, setting Environment variables
environment variables 7, 15 CLIENT_LOCALE 21
DBLANG 21
DBPATH 22
C INFORMIXDIR 7, 19, 20, 21
INFORMIXSERVER 22
Client SDK
LD_LIBRARY_PATH 15
installation scripts for 13
PATH 7, 15
products, list of 2
problem resolution 7, 16
using 16
TERM 16
CLIENT_LOCALE environment
TERMCAP 16, 21, 22
variable 21
Error messages. See
C shell, setting environment
Troubleshooting.
variables 7, 15
D F
Files
Database server
group 5
cannot connect to 23
[Link] 16
installation scripts for 13
passwd 5
using 16
registry 17
DBLANG environment variable 21
sqlhosts 16
DBPATH environment variable 22
termcap 16
Default installation directory 6
Dependencies, software 1
Documentation notes
filename for 12
G
location 11 Global Language Support. See GLS.
GLS
location of files for 17
problem resolution 21
group file 5
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z @
I L R
Informix product files LD_LIBRARY_PATH environment Red Hat Package Manager. See
loading 10 variable 15 RPM.
uninstalling 11 License S/N. See Serial number. registry file 17
Informix products Linux operating system Release notes
list of 1 patches, obtaining 5 filename for 12
localizing 17 patches, problems if missing 22 location 11
problem resolution 21 preparing for Informix RPM
using 16 installation 4 database
INFORMIXDIR directory Loading distribution files 10 creating an entry 9
ownership 15 Locale 17 querying for installed
INFORMIXDIR environment packages 11
variable printing package information 9
problems caused by 19, 20, 21 M querying Informix binary
setting 7 packages 9
Machine notes
where needed 13 trouble shooting 17
filename for 12
INFORMIX-Driver for JDBC rpm command
location 11
downloading 2 -e option 10
Memory, shared 22
installing 15 examples 10
Message 32766 21
INFORMIXSERVER environment -i option 9
variable 22 Runtime problems 22
informix, user and group 5
Installation
O
after rpm exits 13 [Link] file 16 S
Client SDK 13 On-line files
Serial number
directory for 6 documentation notes 11
obtaining 2
Dynamic Server 13 machine notes 11
setting 14
environment variables for 6 release notes 11
troubleshooting 20, 21
INFORMIX-Connect 13
Shared memory 22
INFORMIX-Driver for JDBC 15
Software dependencies 1
loading files for 9 P Software serial-number key. See
login for 4
Package files Serial number.
of multiple Informix products 3
for Informix products 1 sqlhosts 16
running scripts 13
naming conventions 8 stty command 20
troubleshooting 19
Package names 8
installclientsdk script 13
Package-manager utility. See RPM.
installconn script 14
installserver script 13
passwd file 5 T
PATH environment variable
tar command 15
adjusting 7
TERM environment variable 16
INFORMIXDIR in 7
K INFORMIX-Driver for JDBC in 15
TERMCAP environment
variable 16, 21, 22
Key card. See Serial number. Products included in this
Terminal-display distortion 22
distribution 1
Troubleshooting
arguments to --prefix must begin
with a / 18
cannot attach to shared
memory 22
command not found. 21
common problems 17
informix must exist to install
product 18
INFORMIXDIR, messages
about 19
install scripts 19
installclientsdk script 19
installconn script 19
installserver script 19
message number 32766 20
must be root to install
product 17, 19
post-installation 22
product usage 22
rpm binary package cannot be
installed 18
rpm error messages 17
runtime problems 22
serial number 19, 20, 21
starting products 21
U
Uninstalling 11
User informix, creating 5
V
Version compatibility 4
Symbols
/opt/informix directory 6
Index 3
Common issues during Informix installation include entering an invalid serial number, which can occur due to typing errors and might be fixed by double-checking and re-entering the correct values. If the installation script reports an unknown message number, it could indicate that INFORMIXDIR was not set correctly. Problems of command not found usually link to incorrect INFORMIXDIR or PATH settings. Resolving these typically involves verifying and correcting these environment variables, ensuring accurate typing of keys, and following steps outlined in the documentation .
To prepare the package-manager environment, it's critical to distinguish package files from binary packages. Ensure the Informix package files are correctly located on the system, possibly involving mounting a drive. Package information can be queried using RPM commands such as rpm -qpi to understand more about a product’s release. These preparatory steps facilitate smooth installation, helping avoid issues such as executing commands as non-root users or misplacing package directories .
Environment variables like INFORMIXDIR and PATH are crucial for the installation and configuration of Informix products on Linux. They ensure that the system can locate the necessary executable files and libraries. INFORMIXDIR should be set to the directory where Informix is installed, typically /opt/informix. PATH should include the Informix binary directory, typically appended as $INFORMIXDIR/bin. Additionally, for terminal operation, TERM and TERMCAP may need to be configured to ensure correct display and interaction characteristics . If these variables are not set correctly, installation and operation failures are likely, such as inability to find commands or incorrect environment setup messages .
The RPM package manager handles the pre-installation of Informix software by transferring pre-installation files to the hard drive but does not perform actual installations. Users can query package information using commands like rpm -qp to list packages and rpm -qpi for detailed package data. To extract a package, users must ensure they're logged in as root, mount any necessary drives, and use the rpm -i command to install the desired packages. This command checks for the existence of the user and group informix, creates needed directories, and records package installation details in the RPM database .
Incorrect environment variables can significantly affect the startup and performance of Informix client products. For instance, if INFORMIXDIR points to the wrong directory, or if DBLANG or CLIENT_LOCALE are set incorrectly, users may encounter errors like 'Unknown message number 32766'. Misconfigured PATH variables may prioritize wrong executables, leading to 'Command not found' errors. Hence, accurate setup of these variables is essential for proper functionality .
To uninstall Informix packages on Linux, log in as root and use the rpm -e command, ensuring it removes the product files and directories as well as the entry from the RPM database. It's essential not to use the full package file name during uninstallation. Keep in mind the rpm -e command will not remove any files or directories created by the installation scripts beyond those necessary for the package .
If an 'Invalid serial number' message appears, recheck and re-enter the correct serial number and key, ensuring they're typed accurately. It's important because misinterpretations during typing can cause this error. Setting the erase character is crucial as the installation script might misinterpret certain keystrokes; for example, mistaking a backspace for a regular character. This is set using the command stty erase CTRL-h. Ensuring these steps can prevent installation termination due to input errors .
Critical files and environment variables for connecting to an Informix database server include sqlhosts, /etc/hosts, /etc/services, INFORMIXSERVER, and SQLEXEC. Errors or typographical mistakes in these can prevent connections to the database server. For example, if INFORMIXSERVER is misconfigured, the client cannot resolve the database server address. Ensuring correct values in these variables and files is vital for successful connections .
A package file in the Informix installation context contains the entire software package, including a preamble describing the package. In contrast, a binary package is a compressed archive within this file containing an installation utility, sample configuration files, and executable libraries. Importantly, the RPM package-manager doesn't install these directly but prepares the necessary files for installation by specific utilities contained within each package .
If networking problems or unexplained crashes occur, verify if the Linux operating system is fully patched as unpatched systems can cause these issues. Check the machine-notes file in the $INFORMIXDIR/release/en_US/0333 directory for specific patch information. It's essential to keep the system updated to avoid these problems .