Installing Ingres

How You Install Ingres

If you are installing Ingres for the first time, you should be familiar with the Installation Considerations before installing the software.

The process for installing Ingres in any operating system environment is as follows:

1. Verify that your hardware and software meet the Ingres requirements, as documented in the Readme for your platform.
2. Decide on file locations, as described in File Location Guidelines and DBMS Server Disk Configurations.
3. Install the software.
4. Perform post-installation tasks.

Installing Ingres for Linux

Ingres is installed on Linux using RPM Package Manager. You can install Ingres using an installation wizard or from the command line.

Note: Installation of Ingres requires root access. If you are logged in as another user, you will need the root password.

Install Ingres for Linux Using the Installation Wizard

The installation wizard easily installs Ingres without your having to know RPM commands.

To start the installation wizard

1. Run the ingres_install script located in the root directory of the Ingres distribution.

   The first page of the Ingres Installation Wizard is displayed.

2. Respond to the Installation Wizard dialogs.

   If you need more information about a specific item, click the item's information button.

   After you provide the required information in the Installation Wizard dialogs, the installation program installs Ingres.

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 ingres_express_install command
• Using RPM commands

ingres_express_install Command—Install Ingres

The ingres_express_install command quickly installs Ingres RPM packages.

This command has the following format:

ingres_express_install [instance_ID] [instance_location]

• instance ID

  Specifies the Ingres instance ID to use for the instance.

• instance_location

  Identifies the directory into which you want to install Ingres.

Examples: ingres_express_install Command

This command installs all RPM packages in the current working directory with the default configuration:

ingres_express_install

This command installs all RPM packages with the default configuration, but with an instance ID of A1:

ingres_express_install A1

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.

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

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

1. Create a response file that defines the configuration.
2. Specify the name of the response file on the II_RESPONSE_FILE environment variable.
3. Install the RPM packages by either using the ingres_express_install command or invoking RPM directly.

Response File—Define Configuration for Custom Install

The response file defines the configuration for your Ingres instance. You can use any name for the response file.

Each entry in the response file must be on a separate line and is a name-value pair, as follows:

variable=value

where variable is an Ingres response file parameter name.

Commonly used variables are listed in Installation Parameters.

Example: Response File to Install Ingres as a Two-Disk System

The following response file shows Ingres installed on two disks, as follows:

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

II_DATABASE=/disk2

II_DUAL_LOG=/disk2

II_TIMEZONE_NAME=JAPAN

II_CHARSET=KANJIEUC

Example: Response File to Install Ingres as a Four-Disk System

The following response file shows Ingres installed on four disks, as follows:

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

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=NA-EASTERN

II_ENABLE_SQL92=ON

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.

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 Ingres2006-9.0.4.rpm to use an II_INSTALLATION of XX, issue the following command:

iirpmrename [path_to_directory/]Ingres2006-9.0.4.rpm XX

A new RPM package is created in the current working directory called Ingres-XX-9.0.4.rpm. The package will install with II_SYSTEM=/opt/Ingres/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

Follow these instructions to safely upgrade any Ingres release using RPM.

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 Migration Guide.

   Important! Files that you have customized will be lost during the upgrade. Copy your customized files to a safe place. For more information, see the Migration Guide.

2. Issue the following command to see the list of Ingres RPM packages installed for the instance to be upgraded:

   rpm -q --whatrequires core_pkg_name

   where core_pkg_name is the core package name for the release, for example, ca-ingres (for Ingres r3) or ingres2006 (for Ingres 2006).

   Note: If you are upgrading an instance that was installed using RPMs that were renamed to embed an instance ID, then use "core_pkg_name-XX" 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 -ivh 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 -ivh --replacefile --replacepkgs \

   complete list of RPM files to be installed

   For any other instance location:

   rpm -ivh --replacefiles --replacepkgs --prefix <II_SYSTEM> \

   complete list of RPM files to be installed

5. Remove the RPM package information for the old instance, as follows:
   1. Find the correct packages:

      rpm -q --whatrequires core_pkg_name

   2. If the list returned is satisfactory, remove the packages:

      rpm -q --whatrequires ca-ingres | xargs rpm -e --justdb

   3. Remove the RPM package information for the old core package. Include the version and the package name, for example:

      rpm -e --justdb core_pkg_name-x.y.z

      where x.y.z is the version number (for example, 3.0.3 for Ingres r3, or 9.0.4 for Ingres 2006).

Notes:

• If you used rpm -Uvh with --prefix to upgrade an instance, binary and other installed files (for example, iimerge) may be removed. Should this occur, simply re-run the same command using the additional flags replacefiles and --replacepkgs, and all the missing files will be replaced. Database or configuration files will not be affected.
• For the special case where you are upgrading from a non-NPTL build to a NPTL build with the same version number, you must upgrade using the following command:

  rpm -ivh --replacefiles --replacepkgs new-package-list

Install Ingres for Windows

The installation process on Windows uses an easy to follow setup wizard.

To start the Ingres Setup Wizard

1. Log on to your Windows machine and execute the file setup.exe located in the root directory of the Ingres distribution.

   Note: To install Ingres, you must be logged on as a user with administrative privileges.

   The first page of the Ingres Setup Wizard is displayed.

2. Respond to the setup wizard dialogs.

   If you need more information about a specific item, click the item's information button .

   After you provide the required information in the setup wizard dialogs, the installation program installs Ingres.

Separately Installed Components

The Ingres .NET Data Provider and Ingres Documentation are provided as separately installable components. They are displayed as installable components in the setup wizard only if their packages are detected in the installation image you downloaded. When a full Ingres image (Ingres, Ingres .NET Data Provider, and Ingres Documentation) is installed, these three components are listed as separate programs in the Add/Remove Programs feature of the Control Panel in Windows.

Note: If you download the Ingres .NET Data Provider and Ingres Documentation packages to the same directory as the Ingres download, they will appear as installable components.

Advanced Component Selection

The Component Selection page of the setup wizard lets you select a Custom installation.

When Custom is selected, the checkbox "Select advanced customization of components" appears. This option lets you select individual components (rather than default packages) for installation. For example, Vision and network protocols other than TCP/IP are not installed by default, so you can select these individually using the advanced Custom Setup.

This option is recommended for advanced users only.

Perform a Silent Install on Windows

You can use the installer on Windows in response file mode to create a response file to support an unattended (silent) installation of Ingres.

To create a response file using the Windows installer

1. From the root directory of the Ingres distribution, execute the following command:

   setup.exe /c

   A message informing you that the installer is running in response file mode is displayed. Click OK to display the first page of the Ingres Setup Wizard.

2. Respond to the Ingres Setup Wizard dialogs to select the platform, components and configuration settings for your Ingres instance.
3. Review the default storage location and file name for the response file when prompted on the following dialog.

   

   To change the default location or file name, click Change, enter the new information and then click OK.

   Note: The response file must be in a directory that is globally readable, or the install process will fail.

4. Click Finish to create the response file.

   If you want to review the response file parameter settings in a text editor, click Yes when prompted. Otherwise, click No to exit the Ingres Setup Wizard.

   

   Once created, a response file can be opened with any text editor, reviewed, and modified manually if changes are required to any of the values selected during the response file creation process.

To install Ingres using a response file

Issue the following command from the root directory of the Ingres distribution:

setup /r path/response_file_name

• path

  Specifies the full storage location path for the response file.

• response_file_name

  Specifies the name of the response file.

Example setup /r command

C:\Ingres2006\cdimage\setup /r C:\Ingres2006\myresponsefile.rsp

Install Ingres for UNIX

Ingres for UNIX can be installed in interactive mode using a form-based utility.

To install Ingres on UNIX using the forms-based Ingres Installation Utility

1. Log in as the root user.
2. Extract all files from the "CD Image" saveset that was downloaded from the Ingres web site to a local directory (or insert the CD-ROM into the drive and mount the drive from a local host, if not mounted automatically).
3. Change to the root directory on the directory where you extracted the "CD Image" saveset files or the CD-ROM, and enter the following command to run the install utility:

   % install.sh

   The forms-based Ingres Installation Utility is started.

4. Respond to the install dialogs.

   Ingres components are installed on your system.

More information:

Installing Ingres on UNIX

Install Ingres for OpenVMS

To install Ingres on OpenVMS, you execute the VMSINSTAL utility. VMSINSTAL runs the installation and setup scripts, which prompt you for the appropriate directory locations and other necessary information. (For specific information about VMSINSTAL, see your OpenVMS documentation.)

Note: Before running the install program, make a complete backup of your system.

Note: Upon completion, the install utility checks your current system resources—that is, the resources available during installation—to ensure that you can run Ingres as configured. You may want to perform the installation while running any non-Ingres programs that will typically run at the same time to determine the resources that will be available to Ingres.

To install the Ingres software on OpenVMS

1. At the operating system prompt, enter

   $ @sys$update:vmsinstal * distribution_medium

   The distribution_medium is the name of one of the following:

   • A physical device, such as a CD-ROM drive, which holds the distribution medium
   • A storage directory containing the files optionally transferred from the distribution medium

     VMSINSTAL initializes the software environment, defines logical names and symbols, and makes validity checks. It also gives you an opportunity to cancel the install process, if you need to make a backup of your current system. If you choose to continue, all user-defined global and local OpenVMS symbols are deleted at that point.

     The program then displays a description and important information about using the installation script.

2. Respond to the program prompts.

   Some prompts display default values in brackets. To accept the default, press Return.

   Enter the value for II_SYSTEM when you see the following prompt:

   Location for this installation:

   If the Ingres directory does not exist, the program creates it.

   If any installed products require configuration, VMSINSTAL asks:

   Do you want to run the configuration IVP following this installation [YES] ?

   Enter y to run the Setup programs immediately after installation; otherwise, enter n to run the Setup programs later.

   A final Installation Summary appears.

3. Confirm the installation summary.

   VMSINSTAL installs the specified products and verifies that each product was transferred properly from the distribution medium. If you selected products that are dependent on other products, VMSINSTAL automatically installs the necessary products.

   The installation finishes or starts executing the setup scripts.

   The software is now installed on your system.

More information:

Installing Ingres on OpenVMS

How You Access the Instance on Linux and UNIX

When the installation is complete, the instance is running.

To access your instance, you must source the environment file that was created during installation.

During installation, an environment file is written to the home directory of the operating-system user ID that was defined during installation (the default is "ingres"). The name of the environment file depends on the value of II_INSTALLATION.

To source the environment file created during installation, issue the following command.

Note: The following examples assume an operating-system user ID of ingres.

For bash:

. ~ingres/.ingXXbash

For tcsh:

source ~ingres/.ingXXtsch

where XX is the instance ID of the instance.

For other users to have access to the instance and the Ingres tools, they must have access to the .ingXXbash and .ingXXtsch scripts. The scripts can be copied to the home directory of any user.