Installation Guide > Installation Guide > Installing Ingres > Installing Ingres for Linux > install Command—Install Ingres
Was this helpful?
install Command—Install Ingres
The install.sh command quickly installs Ingres RPM packages.
This command has the following format:
install.sh [-interactive|-express] [-acceptlicense]
         [-uid uid] [-user username] [-noroot] [-usesudo] [-no32bit]
         [-respfile file] [instance_ID] [install_dir]
         [-licdir dir] [-sparkdownload] [-?|-help]
-interactive
Prompts for all configuration options. (Conflicts with -express.)
Note:  This option is for advanced users only.
-express
(Default) Does not prompt for configuration options. Installs Ingres with the default configuration, as described in Default Installation Configuration. (Implies -acceptlicense; conflicts with ‑interactive.) The -express option installs Ingres with the default configuration.
-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.)
-no32bit
Does not install 32-bit support and Applications-By-Forms (ABF).
 
-respfile file
Uses the settings in the response file during setup. A response file lets you customize the installation. (Requires -express or -acceptlicense; not valid with -interactive.) For more information, see Response File—Define Configuration for the Installation.
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).
-licdir dir
(Required in express mode.) Uses dir as the location of a valid license.xml file. (Not valid with -respfile.)
-sparkdownload
Downloads and configures Apache Spark. Not valid with -interactive.
Note:  install.sh will fail if another instance of Ingres exists with the same instance ID as the one you are installing (RPM only).
Examples: install.sh Command
Install all RPM packages with the default configuration into the default location "/opt/Actian/IngresII":
install.sh -licdir lic_dir
Install all RPM packages with the default configuration into "/opt/Actian/IngresII", but with an instance ID of A1:
install.sh -licdir lic_dir A1
Install all RPM packages with the default configuration into "/opt/Actian/IngresA2", with an instance ID of A2:
install.sh -licdir lic_dir /opt/Actian/IngresA2 A2
Install all RPM packages in interactive mode (prompting for manual configuration):
sh install.sh -interactive
Install all RPM packages with the configuration defined in a response file, resp.txt:
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.
Last modified date: 08/29/2024