How You Install Ingres for Linux Using a Response File
You can install Ingres with a custom configuration at the command line by using a response file. The process 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. 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 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 iisystemd script which is under $II_SYSTEM/ingres/utility. This script configures and starts the instance for the systemd service.
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 iisystemd 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 iisystemd script, specifying the response file.
Note: This step is not necessary if you used install.sh in express mode (that is, with no flags).
To run the service script to configure the instance according to settings in a response file
Issue the following command.
$II_RESPONSE_FILE $II_SYSTEM/ingres/utility/iisystemd -a start -d $II_SYSTEM -r $II_RESPONSE_FILE -s rdbms
The instance is configured and started.
or
$II_SYSTEM/ingres/utility/iisystemd -a configure -d $II_SYSTEM -r $II_RESPONSE_FILE -s rdbms
The instance is configured but not started.