|
|
|
You should thoroughly understand the issues regarding system resources, storage locations, and other configuration parameters before installing Ingres. If you are not sure, have someone more knowledgeable in these areas perform the installation planning.
Before installing Ingres on UNIX, do the following:
|
|
|
Only the system administrator (instance owner) can install Ingres, therefore, you must create this account before installing the product.
Follow this process to create the system administrator account:
If you do not have access to this account, have the UNIX system administrator complete this procedure or log in for you.
This account should have a user identification code (UID) greater than 100.
%ls -lgL /dev/kmem
crw-r----- 1 sys 13, 1 Jun 19 09:05 /dev/kmem
Note: Check the Readme file for your operating system for any variation in this procedure.
|
|
|
Initially, you can configure your installation as one of the following major types. Later, you can install other products or modify parameter settings to add more capabilities to your installation. For example, you can add networking capabilities to a standalone installation that is connected to a network. Or you can add client capabilities to an installation that you initially configured as a networked DBMS Server.
The major configuration options are as follows:
Provides only local access to local databases. This instance includes the Name Server, DBMS Server, and its own set of tools.
Required products: DBMS Server, tools
Allows remote clients to access its databases through a network. (If tools are installed, local users also can access its databases.)
This instance includes the Name Server, DBMS Server, Communications Server, Data Access Server, ODBC driver, and JDBC driver.
By installing Ingres tools and then modifying the Ingres Net connection data, you can add outgoing client capabilities to a networked DBMS Server instance. Doing so enables it to act both as a client of a remote DBMS Server and as a DBMS Server to its own remote clients.
Required products: DBMS Server, Ingres Net, ODBC driver, JDBC driver, Ingres tools (optional, but required for local access to local databases)
Allows access to multiple databases—local and remote, Ingres and non-Ingres—simultaneously. This instance includes Ingres Star, Name Server, DBMS Server, Communications Server, Data Access Server, ODBC driver, and JDBC driver. It may also contain Ingres tools.
Required products: DBMS Server, Ingres Net, ODBC driver, JDBC driver, Ingres Star, Ingres tools (optional)
Has its own set of Ingres tools and accesses databases on a networked DBMS Server instance on a remote node. This installation includes the Name Server, Communications Server, Data Access Server, ODBC driver, JDBC driver, and Ingres tools. It does not contain the DBMS Server.
You can configure a networked DBMS Server instance as a client of another DBMS Server on a remote node. To do so, install Ingres tools on the DBMS Server, and then add client capabilities by modifying the Ingres Net connection data.
You can set up a client in a different environment to access an Ingres database in your current environment. For example, a client in a Windows environment can access a database in a Linux environment. For more information, see the Connectivity Guide.
Required products: Ingres Net, ODBC driver, JDBC driver, Ingres tools
Uses a Network File System to share all Ingres files on a networked DBMS Server instance. This instance contains no Ingres files on its own node.
Required products: A networked DBMS Server instance on a node in the Network File System. The ingmknfs utility must be run to create the NFS client instances and configure the DBMS Server for NFS-client use.
|
|
|
The process for installing and configuring Ingres on UNIX is as follows:
Note: This step is necessary only if the install procedure did not include this step, for example, if you used the Install method in Interactive mode.
|
|
|
Ingres on UNIX can be installed using one of the following modes:
|
|
|
The ingres_express_install command quickly installs all Ingres packages.
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.
This command has the following format:
ingres_express_install [instance_ID]
Specifies the Ingres instance ID to use for the instance.
Examples: ingres_express_install Command
This command installs all packages in the current working directory with the default configuration:
ingres_express_install
This command installs all packages with the default configuration, but with an instance ID of A1:
ingres_express_install A1
|
|
|
In interactive mode, you install Ingres using a form-based utility.
To install Ingres on UNIX using the forms-based Ingres Installation Utility
% install.sh
The forms-based Ingres Installation Utility is started.
Ingres components are installed on your system.
|
|
|
In command line mode, you can completely automate and customize your install by supplying the appropriate arguments to the ingbuild command at the operating system prompt.
|
|
|
The ingbuild command installs Ingres.
Ingbuild runs in interactive mode if you specify no command line arguments or only -mkresponse or -exresponse.
Ingbuild runs in batch mode (without interruption) if you specify a distribution medium. It also automatically starts any needed setup programs for the installed products, unless the nosetup option is specified.
This command has the following format:
ingbuild [flags] [distribution_medium]
Specifies zero or more install flags, as follows:
Installs all products (default). This flag is valid when a distribution medium is specified.
Installs only those products you list. Use a comma to separate each item in the list. This flag is valid when a distribution medium is specified.
Displays a list of the products on the distribution medium, which you can then specify with the install flag or -version flag. This flag should not used in combination with other flags.
Displays the version number of the instance (when specified without list) or displays the version of the requested packages (when specified with list). Use commas to separate items in the list. This flag should not used in combination with other flags.
Does not run setup programs. This flag is valid when a distribution medium is specified.
Runs setup programs using default values. This flag is valid when a distribution medium is specified.
Accepts Ingres license and bypasses license prompt. This flag is valid when a distribution medium is specified.
Ignores any errors encountered during file copy. This flag is valid when a distribution medium is specified.
Displays ingbuild command options. This flag is valid when a distribution medium is specified.
Creates a response file that contains install parameters, but does not install the product. This flag is valid only in an interactive install, and is mutually exclusive with the -exresponse flag.
Reads installation parameters from a response file during an interactive install. This flag is valid only in an interactive install and is mutually exclusive with the -mkresponse flag.
Identifies a response file name other than the default for use with -mkresponse or -exresponse.
Default: ingrsp.rsp
Specifies the name of the distribution medium on which the software to be installed resides. A batch, rather than interactive, install is executed. This parameter is required with the -all, -install, -express, ignore and nosetup flags. If a distribution medium is provided with no flag, -all is assumed.
The distribution medium is one of the following:
Examples: ingbuild command
% ingbuild -help
% ingbuild -products
% ingbuild -all distribution_medium
|
|
|
The setup programs configure the installed components.
You must run the setup programs if the installation process did not perform this step if you used the Install method in Interactive mode—or if you want to change the default values.
After installing Ingres components, you can run the setup programs at any time from the Currently Installed Components screen.
The order in which you run the setup programs is important. For a networked DBMS Server instance, run the setup program for the DBMS Server before running Ingres Net Setup. Ingres Net Setup can then use several of the values you specified for the DBMS Server.
To run the setup programs from the Currently Installed Components screen
The setup programs execute one after another, in an appropriate order.
Note: If you need to set up components individually, highlight the appropriate row for the component you want to set up and choose Setup from the menu.
When setting up required parameters, default values sometimes appear in brackets after the prompt. To accept a default value, press Return. Otherwise, enter an appropriate value and press Return.
The Setup program(s) prepare each component for use.
|
|
|
You create and configure NFS client instances using the ingmknfs utility, rather than the install and setup programs.
The process for installing and configuring an NFS client is as follows:
You can issue the ingmknfs command in either of the following ways:
|
|
|
To set up each NFS client individually, follow these steps:
For C shell:
% setenv II_SYSTEM pathname
For Bourne shell:
$ II_SYSTEM=pathname; export II_SYSTEM
Details are described in NFS Client Parameters (UNIX).
For C shell:
% set path=($II_SYSTEM/ingres/{bin,utility} $path)
% rehash
For Bourne shell:
$ PATH=$II_SYSTEM/Ingres/bin:$II_SYSTEM/ingres/ utility:$PATH
$ export PATH
% ingmknfs
The program then asks:
Do you want to authorize any users at this time? (y/n) [y]
Enter n if you prefer to create the authorization entry later, using either the netutil utility (see the Command Reference Guide), or the Network Utility or Visual DBA (see the Connectivity Guide).
When done, you are returned to the operating system prompt.
|
|
|
To set up one or more NFS clients from the server, follow these steps:
% ingmknfs host {host}
For example, if your DBMS Server node is "sales" and your client nodes are "region1," "region2," and "region3," you would enter the following command on the DBMS Server node:
% ingmknfs region1 region2 region3
When done, you are returned to the operating system prompt.
% setenv II_SYSTEM pathname
For C shell:
% set path=($II_SYSTEM/ingres/{bin,utility} $path)
% rehash
For Bourne shell:
$ PATH=$II_SYSTEM/ingres/bin:$II_SYSTEM/ingres/utility:$PATH
$ export PATH
|
|
|
The TERM_INGRES environment variable defines the terminal type you are using. You can enter a value for the TERM_INGRES environment variable in response to a prompt during installation or prior to running the install program.
To set TERM_INGRES
Enter the following command at the operating system prompt:
% setenv TERM_INGRES Ingres_terminaltype
For example, the following command defines your terminal as a VT100.
For C shell:
% setenv TERM_INGRES vt100
For Bourne shell:
$ TERM_INGRES=vt100; export TERM_INGRES
|
|
|
The II_DISTRIBUTION environment variable stores the full path name for the device or file containing the Ingres distribution.
You can enter a value for the II_DISTRIBUTION environment variable in response to a prompt during installation or prior to running the install program.
Note: For faster file transfer during the installation process, you can copy the contents of the distribution medium to a disk file as an intermediary step, and then specify the disk file as the pathname for II_DISTRIBUTION.
To set II_DISTRIBUTION
Enter the following command at the operating system prompt:
For C shell:
% setenv II_DISTRIBUTION pathname
For Bourne shell:
$ II_DISTRIBUTION pathname; export II_DISTRIBUTION
|
|
|
Post-installation tasks include the following:
|
|
|
The transaction log file can be a raw device rather than an ordinary file system file. A raw device is a disk partition without a file system. This avoids file system overhead for disk input and output. Ingres supports use of a raw device for the transaction log files as a highperformance option.
By default the install process creates the log file as an ordinary file. After Ingres is installed, you can create and configure the transaction log file as a raw device.
|
|
|
The following restrictions apply to the locations for a raw log file:
|
|
|
After Ingres is installed, you can create and configure the transaction log file as a raw device.
Note: Check the Readme file for any variations to this procedure that are specific to your platform.
To create and configure a raw log file
(If you do not have access to this account, have the UNIX system administrator complete this procedure or log in for you.)
For more information about creating a raw device, see the UNIX documentation.
ls -l /dev
This command should return output similar to this example:
crw-r----- 1 root 17, 3 Dec 16 12:52
/dev/rsd1d
brw-r----- 1 root 11, 3 Dec 16 12:52
/dev/sd1d
For C shell:
% setenv II_SYSTEM dirname
% set path = ($II_SYSTEM/ingres/{bin,utility} $path)
% cd $II_SYSTEM/ingres
For Bourne shell:
$ II_SYSTEM=dirname
$ export II_SYSTEM
$ PATH=$II_SYSTEM/ingres/utility:$II_SYSTEM/ingres/
bin:$PATH
$ export PATH
$ cd $II_SYSTEM/ingres
% mkrawlog
The mkrawlog command:
Note: All raw partitions of a multi-partition raw log file must be the same size.
The raw log file is configured.
|
|
|
You can have Ingres start up and shut down automatically. To add an automatic startup command, you must know the startup mechanism your environment uses. See the administration manual for your UNIX environment, or ask your system administrator to assist.
Typically, UNIX startup scripts are organized either in directories by run-level, or in startups scripts in /etc.
Note: For additions or variations necessary for your platform, see the Readme file.
If your environment uses the "directory-by-run-level" method, we recommend that you sequence your Ingres script so that it starts late in the startup sequence, and shuts down early in the shutdown sequence.
If your environment uses one or a few startup scripts, edit the rc.local script. Look for a shell function called localrc, or simply add the Ingres startup near the end.
When writing the Ingres startup script, make sure that you set all necessary shell environment variables, and run the ingstart command as instance owner. At a minimum, you must set II_SYSTEM and PATH. In most UNIX environments, you must also set the shared library path (LD_LIBRARY_PATH, LD_LIBRARY_PATH_64, LIBPATH, SHLIB_PATH, or SH_LIB_PATH).
For example:
II_SYSTEM=/inghome; export II_SYSTEM
PATH=$PATH:$II_SYSTEM/ingres/bin:$II_SYSTEM/ingres/utility; export PATH
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$II_SYSTEM/ingres/lib
export LD_LIBRARY_PATH
su ingres -c "ingstart"
If shared libraries are not supported on your operating system, there is no need to set the shared library path variable.
Depending on your UNIX environment, you may want to redirect the output of the ingstart command to a file or to /dev/console.
You must add the appropriate commands to the system startup file on each machine running a DBMS Server or client.
|
|
|
If your operating system has shadow passwords and you are not using the Ingres installation password authorization, you must install the password validation program to allow access to the networked DBMS Server.
To install the password validation program
The mkvalidpw script installs the password authorization program used by the DBMS Server.
|
|
|
The install process identifies only the owner of the system administrator account to your instance to permit authorized access to the databases.
To enable users to access tools and databases, the system administrator must do the following:
For more information, see the System Administrator Guide.
|
|
|
To facilitate user access to Ingres tools when they log in to the system, add the following access commands to the users' login files, where installation_location is the storage location for your instance's system files (executables).
For C shell, add the following command to each user's ".cshrc" file:
% setenv II_SYSTEM installation_location
% set path=($II_SYSTEM/ingres/bin $path)
For Bourne shell, add the following command to each user's ".profile" file:
$ II_SYSTEM=installation_location; export II_SYSTEM
$ PATH=$II_SYSTEM/ingres/bin:$PATH; export PATH
|
|
|
To support shared libraries on your operating system, include the following command in each user's path. For the name of the library variable (lib_variable) for your platform—for example, LD_LIBRARY_PATH, LD_LIBRARY_PATH_64, LIBPATH, SHLIB_PATH, or SH_LIB_PATH—see the Readme.
For C shell:
% setenv lib_variable
/lib:$II_SYSTEM/ingres/lib:$lib_variable
For Bourne shell:
$ lib_variable=/lib:$II_SYSTEM/ingres/lib: $lib_variable
$ export lib_variable
|
|
|
After you have completed the install process and started the instance, you can use the install utility with your current instance.
To view the contents of your current instance
% cd $II_SYSTEM/ingres
install/ingbuild
The initial screen of the install utility appears, with the following menu options:
CustomInstall PackageInstall Current Help Quit
Note: The Current option appears only if products are installed.
The Currently Installed Components screen appears.
All Ingres components that are installed are listed.
|
|
|
The Currently Installed Components screen of the Install utility lets you perform various functions on your current installation, including the following: