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:

1. Create a response file (see Response File--Define Configuration for the Installation) that defines the configuration.

2. Set the II_RESPONSE_FILE environment variable (see Set the II_RESPONSE_FILE Variable) to the absolute path and name of the response file.

3. Install the RPM packages by either using the ingres_express_install.sh command (see ingres_express_install Command--Install Ingres) or invoking RPM directly (see Install Ingres Using RPM Commands).

4. If you invoked RPM directly, run the service script specifying II_RESPONSE_FILE (see 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:

where variable is a response file parameter name.

Commonly used variables are listed in Installation Parameters. A more extensive list is in Response File Parameters.

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 located 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:

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

The machine has two CPUs, requires a 500 MB transaction log, and is located 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:

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:

export II_RESPONSE_FILE=path_to_directory/response file name

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 ingres_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 /sbin/service utility does not preserve any environment variables so II_RESPONSE_FILE must be passed as an argument, as follows:

/sbin/service ingresXX configure $II_RESPONSE_FILE

where XX is the instance ID.

Alternatively, you can run the service script directly, which automatically uses II_RESPONSE_FILE: