Installing Ingres for Linux at the Command Line
You can install the Ingres RPM packages at the command line by doing either of the following:
• Using the express_install command
• Using the RPM command
express_install Command—Install Ingres
The express_install.sh command quickly installs Ingres RPM packages.
This command has the following format:
express_install.sh [-interactive|-express] [-acceptlicense]
[-uid uid] [-user username] [-noroot] [-usesudo]
[-respfile file] [-?|-help] [instance_ID] [install_dir]
[-licdir dir]
-interactive
Prompts for all configuration options. (Conflicts with -express.)
Note: This option is for advanced users only.
-express
Does not prompt for configuration options. (Implies -acceptlicense; conflicts with ‑interactive.) The -express option installs Ingres with the default configuration, as user “ingres”.
-acceptlicense
Accepts all license prompts.
-uid uid
Specifies the user ID (UID) to be used when creating user. The user name must exist. (Disallowed with -noroot.) (Not valid for RPM and DEB.)
-user username
Installs Ingres as username instead of ingres. The user name must exist. (Disallowed with ‑noroot.)
-noroot
Installs Ingres as the current user. All installation locations must exist and be writable as current user for the installation to succeed. (Not valid for RPM or DEBs.) Instance will be owned by the current user.
-usesudo
Installs Ingres using the current user and invokes sudo for root access, locally and remotely. The instance is owned as "ingres" by default. If required, the current user is used for remote connections and sudo is invoked for root access. (Not valid for RPM or DEBs or as root user.)
-licdir dir
Uses dir as the location of a valid license.xml file. (Not valid with -respfile.)
-respfile file
instance_ID
Defines a two-character string where the first character must be an uppercase letter and the second character must be an uppercase letter or a number from 0 to 9.
Default: II
install_dir
Identifies the full path to the location where Ingres is to be installed (II_SYSTEM).
Note: Not valid for DEBs, hard coded to: /opt/Actian/Ingres
Default: /opt/Actian/IngresII
Note: express_install.sh will fail if another instance of Ingres exists with the same instance ID as the one you are installing (RPM only).
Examples: express_install.sh Command
This command installs all RPM packages in the current working directory with the default configuration:
express_install.sh
This command installs all RPM packages with the default configuration into "/opt/Actian/IngresII", but with an instance ID of A1:
express_install.sh A1
This command installs all RPM packages with the default configuration into "/opt/Actian/IngresA2", with an instance ID of A2:
express_install.sh /opt/Actian/IngresA2 A2
This command installs all RPM packages with the configuration defined in a response file, resp.txt:
express_install.sh -respfile /path/to/resp.txt
Note: If you set II_RESPONSE_FILE to point to a valid response file, then you can install Ingres with the configuration defined in that response file.
Installing Multiple Instances
The express_install program cannot be used to install another instance on the same machine. If you want to install another instance, follow these steps:
Install Ingres Using RPM Commands
As an alternative to using the express install script, you can install Ingres by invoking RPM directly.
To install a single package
Invoke RPM with the appropriate installation flags, including the path to the package you want to install, as follows:
rpm ‑ivh path_to_directory/Ingres_package.rpm
To install more than one package at a time
Pass multiple file names, specifying the path to each package, as follows:
rpm ‑ivh path_to_directory/Ingres_package.rpm path_to_directory/Ingres_package2.rpm path_to_directory/Ingres_package3.rpm
To install all packages in the same directory
Specify the following:
rpm ‑ivh path_to_directory/*.rpm
To install a package into a non-default location (that is, with an II_SYSTEM value other than the default)
Use the ‑prefix flag when invoking RPM. The following command installs the specified package with II_SYSTEM=/home/ingres/IngresII:
rpm ‑ivh ‑‑prefix=/home/ingres/IngresII path_to_directory/Ingres_package.rpm
Notes:
• All packages installed in a single instance must have the same value of II_SYSTEM. If you use the prefix flag to install the base package, you must install all subsequent packages with the same –prefix value.
How You Install Ingres with a Custom Configuration at the Command Line
The process for installing Ingres for Linux as a custom configuration at the command line is as follows:
4. If you invoked RPM directly, run the service script specifying II_RESPONSE_FILE.
Response File—Define Configuration for the Installation
A response file contains parameters that define how an instance is to be installed and configured. You can use any name for the response file.
Each entry in the response file must be on a separate line and in the following form:
variable=value
where variable is a response file parameter name.
Commonly used variables are listed in
Installation Parameters on page 34. A more extensive list is in
Response File Parameters on page 1.
Example: Response File to Install Ingres as a Two-Disk System
The following response file shows Ingres installed on two disks:
• Disk 1—System files, checkpoint, journal, work, and dump locations, and transaction log
• Disk 2—Databases and backup transaction log
The machine has one CPU, is in Tokyo, and requires the KANJIEUC character set.
Note: The checkpoint, journal, work, dump, and transaction log locations all reside in the default location for the system files (II_SYSTEM), so you do not need to specify a location.
The response file for this configuration is as follows:
II_DATABASE=/disk2
II_DUAL_LOG=/disk2
II_TIMEZONE_NAME=ASIA-TOKYO
II_CHARSET=KANJIEUC
Example: Response File to Install Ingres as a Four-Disk System
The following response file shows Ingres installed on four disks:
• Disk 1—Checkpoint, journal, and dump locations
• Disk 2—System files, transaction log, work files
• Disk 3—Databases
• Disk 4—Backup transaction log
The machine has two CPUs, requires a 500 MB transaction log, and is in New York. You want the database to comply with the ANSI/ISO Entry SQL-92 standard.
The response file for this configuration is as follows:
II_DATABASE=/disk3
II_CHECKPOINT=/disk1
II_JOURNAL=/disk1
II_DUMP=/disk1
II_WORK=/disk2
II_LOG_FILE=/disk2
II_DUAL_LOG=/disk4
II_LOG_FILE_SIZE_MB=500000
II_NUM_OF_PROCESSORS=2
II_TIMEZONE_NAME=AMERICA-NEW_YORK
II_ENABLE_SQL92=ON
Configure and Start the Instance
When installing Ingres using the RPM command, the setup portion of the installation process must be completed by running the service script ingresXX, which is located under /etc/init.d. The service script configures and starts the instance.
You must run the service script specifying a response file that contains II_LICENSE_DIR=/path_to_license_directory; otherwise, you will not be able to configure and start the installation.
Set the II_RESPONSE_FILE Variable
To install a custom configuration, you must set the Ingres environment variable II_RESPONSE_FILE to the name of response file that contains the configuration settings. Use the absolute pathname.
To set the II_RESPONSE_FILE variable, use the following command:
For bash:
export II_RESPONSE_FILE=path_to_directory/response file name
For tcsh:
setenv II_RESPONSE_FILE path_to_directory/response file name
Note: The response file must be in a directory that is globally readable or the install process will fail.
Run the Service Script Specifying II_RESPONSE_FILE
If you installed the instance by using the RPM command directly, and you want to configure the instance using the configuration in a response file, you must run the service script, specifying the response file.
Note: This step is not necessary if you used express_install.sh or the installation wizard.
To run the service script to configure the instance according to settings in a response file
Issue the following command. The /etc/init.d/ingresXX service script does not preserve any environment variables so II_RESPONSE_FILE must be passed as an argument, as follows:
/etc/init.d/ingresXX start $II_RESPONSE_FILE
The instance is configured and started.
or
/etc/init.d/ingresXX configure $II_RESPONSE_FILE
The instance is configured but not started.
where XX is the instance ID.
Rebuild RPM Package with Unique Name
To install multiple Ingres instances on one machine, you need a unique set of package names for each instance. You must rebuild each RPM package to include an instance ID that is unique to the machine. You can then install this package using the instructions described in
Install Ingres Using RPM Commands.
To rebuild the package, use the iirpmrename command. Multiple RPMs can be specified for renaming.
For example, to rebuild the base package named ingres-10.0.1-100.rpm to use an II_INSTALLATION of XX, issue the following command:
iirpmrename [path_to_directory/]ingres-10.0.1-100.rpm XX
A new RPM package is created in the current working directory called ingres-10.0.1-100.rpm. The package will install with II_SYSTEM=/opt/Actian/IngresXX and II_INSTALLATION=XX.
Note: While you can still override the value for II_INSTALLATION using the response file or other methods mentioned above, we do not recommend it.
How You Upgrade Using RPM
The process for safely upgrading any Ingres release using RPM is as follows.
To upgrade Ingres RPMs
1. Make sure the Ingres instance you want to upgrade is completely shut down and that you have taken a backup, as described in the Upgrade Guide.
Note: Files that you have customized will be lost during the upgrade. Copy your customized files to a safe place. For more information, see the Upgrade Guide.
2. Issue the following command to see the list of Ingres RPM packages installed for the instance to be upgraded:
rpm -q --whatrequires ingres
Note: If you are upgrading an instance that was installed using RPMs that were renamed to embed an instance ID, then use "ingresXX” instead of the core package name.
Note: All packages must be upgraded at once. Any attempt to perform an upgrade on a single or smaller group of packages will fail.
3. Log in as root and CD to the directory containing the RPM to be used to perform the upgrade. Make sure variable II_CONFIG is not set.
4. Run rpm -Uvh to install the new RPM packages over the existing instance.
If the instance was originally installed using --prefix to change II_SYSTEM from the default, then this parameter must also be used for the upgrade.
For default instance location:
rpm -Uvh --nopreun --nopostun \
complete list of RPM files to be installed (rpm/ingres...rpm ...)
For any other instance location:
rpm -ivh --nopreun --nopostun --prefix <II_SYSTEM> \
complete list of RPM files to be installed (rpm/ingres...rpm ...)
5. Run the service script to configure and start the instance:
/sbin/service ingresXX start
where XX is the instance ID.