From Ingres Community Wiki

Contents 1 Overview 2 Preparation 3 Installation 3.1 Deploying the files 3.2 Post deployment initialization 4 DBMS Configuration

Overview

Each Ingres distribution contains a set of command line installation scripts or GUI program for installing Ingres, however it is possible to perform an installation using the Red Hat Package Manager (RPM) commands for repeating installations. This article is aimed at Linux users who are familiar with using the command line, for users unfamiliar with Linux command line or Ingres installations should use the alternative installation instructions available from the installation resources wiki page.

The goal of this article is to install a version of Ingres from a release archive of RPM packages, specifying only a limited number of the available packages. The resulting installation should use an instance identifier of X0 and not the default II instance, together with a number of configuration values that differ from the default.

Preparation

The following steps assume:

1. The kernel setting for shmmax is set to a suitable value

   sudo sysctl -w kernel.shmmax=518709248

2. The Linux package rpm-build has been installed (the rpm-build package is required only if the RPM package names require renaming).
3. The Ingres release archive has been downloaded, in this example we are using ingres-10.0.0-128-NPTL-gpl-pc-linux-i386.tgz and should be adjusted according to the released package.
4. The contents of the Ingres release archive has been extracted as the root/admin user.

   tar -zxf ingres-10.0.0-128-NPTL-gpl-pc-linux-i386.tgz

   The extraction should create a top level directory ingres-10.0.0-128-NPTL-gpl-pc-linux-i386 with three sub-directories:

   • bin - Utility scripts

   ./ingres-10.0.0-128-NPTL-gpl-pc-linux-i386/bin

   • pixmaps - icons and images used in the GUI installation program

   ./ingres-10.0.0-128-NPTL-gpl-pc-linux-i386/pixmaps

   • rpm - Ingres packages

   ./ingres-10.0.0-128-NPTL-gpl-pc-linux-i386/rpm

5. Create instance unique package names

   The installed package names need to be uniquely identified and this is achieved by performing a package rename using the iirpmrename utility. To rename all of the packages to include the X0 instance; in the rpm sub-directory run:

cd rpm
../bin/iirpmrename ingres-10.0.0-128.i386.rpm ingres-abf-10.0.0-128.i386.rpm \
ingres-dbms-10.0.0-128.i386.rpm ingres-net-10.0.0-128.i386.rpm \
ingres-odbc-10.0.0-128.i386.rpm ingres-rep-10.0.0-128.i386.rpm \
ingres-star-10.0.0-128.i386.rpm X0 

</ul>

6. Create a response file with the require parameter settings
   • Sample response file

     II_INSTALLATION	X0
     II_CHARSET	UTF8
     II_TIMEZONE_NAME	UNITED-KINGDOM
     II_LOG_FILE_SIZE_MB	512
     II_CONFIG_TYPE	BI

Installation

RPM installation requires that commands are performed as the root or admin user.

Deploying the files

1. Export the environment variable II_HOSTNAME (now probably an obsolete step)

   export II_HOSTNAME=localhost

2. Install the packages

   Core	ingres-X0-10.0.0-128.i386	Common components required by all Ingres packages
   DBMS	ingres-dbms-X0-10.0.0-128.i386	DBMS server components
   NET	ingres-net-X0-10.0.0-128.i386	Net and DAS server components supports remote access

   rpm -Uvh ingres-X0-10.0.0-128.i386.rpm ingres-dbms-X0-10.0.0-128.i386.rpm ingres-net-X0-10.0.0-128.i386.rpm

   -U	This upgrades or installs the package currently installed to a newer version. This is the same as install, except all other version(s) of the package are removed after the new package is installed.
   -v	Print verbose information - normally routine progress messages will be displayed.
   -h	--verbose for a nicer display.

Post deployment initialization

In recent development some of the set-up process was moved from the RPM package into to Run Command (rc) scripts and %posttrans scriptlets. On some versions of Linux the execution of the %posttrans script was not being triggered, as a consequence if installing packages by-hand (not using the express install script or the GUI installer) the set-up process is not run.

Configuration is performed on first start-up or can be manually run using the service start-up.

• Configure the instance with a response file
  • Ensure that the response file is located in a directory where ingres has both read and write permissions

    cp response-file.rsp /tmp/response-file.rsp

  • Use the service command for the Ingres instance to initiate the set-up

    service ingresX0 configure /tmp/response-file.rsp

  • Once completed Ingres is configured and can be started for use

    service ingresX0 start

• First start set-up with default configuration

  service ingresX0 start

  • On completion Ingres is configured, started and ready for use.

DBMS Configuration

DBA and configurations are usually performed as the ingres user.

• Shutdown the instance

  service IngresX0 stop

Some configuration changes require the instance is restarted in order for the new values to be used.

• Source the environment

  . /opt/Ingres/IngresX0/.ingX0bash

• iisetres
  • iisetres is used to set specific configuration values in config.dat from the command line

  iisetres [-v] [+p|-p] name [value]

  For exmaple, to change the system isolation from the default serializable to read committed use

  iisetres -v ii.localhost.dbms.*.system_isolation read_committed

• cbf
  • cbf command starts the Configuration-By-Forms (CBF) utility. The CBF utility displays current values of the server parameters and lets you change them.

  cbf [-host=name] [-node=nodename]

  For example, to change the system isolation from the default serializable to read committed use

• After all configuration changes have been made restart the instance

  service ingresX0 start