Check Ingres Installation on UNIX
To check if the Ingres installation is working fine, follow these steps:
1. Check that you are logged in as the installation owner by issuing the following command at the operating system prompt:
whoami
If the user ID of the installation owner is not shown, log off and log in again as this user.
2. Check that all users have II_SYSTEM set by issuing the following command at the operating system prompt:
echo $II_SYSTEM
/ usr/r6 (this varies by system)
All users must have Ingres executables in their path variables. Check that everyone has the full search path to $II_SYSTEM/ingres/bin.
The installation owner must also include $II_SYSTEM/ingres/utility.
3. Check that each of the Ingres installation variables has a valid value.
Ingres environment variables are only used and “seen” by Ingres and can be displayed with the following command entered at the operating system prompt:
ingprenv
If you are in doubt about the function or legal value of a particular environment variable, see the chapter "Setting Environment Variables and Logicals" and the appendix "Environment Variables and Logicals."
Ingres environment variables denoting installation locations cannot be reset. To change these, you must rerun the installation program, ingbuild, and on UNIX possibly unload and reload your database with unloaddb. More information is provided in
Installation Locations.
4. Check the Ingres environment variables that have been set locally, overriding the Ingres installation-level definitions. Issue the following commands at the operating system prompt:
BSD:
printenv | grep II
printenv | grep ING
System V:
env | grep II
env | grep ING
Only a small category of Ingres environment variables must be defined in the local user environment: those that permit you to access Ingres, and those that define values that are different for your local environment. They include TERM_INGRES and ING_EDIT.
If you trace the problem to a Ingres environment variable setting, correct the value. For details, see "Setting Environment Variables and Logicals." If the installation does not start up, continue with this procedure.
5. Identify your installation code. If there is more than one Ingres installation on this machine, type the following command at the operating system prompt. The installation code is used to distinguish which processes belong to which installation at sites with more than one Ingres installation on the same machine:
ingprenv | grep II_INSTALLATION
The two-letter installation code is displayed (for example, the following code R6):
II_INSTALLATION=R6
Take note of your installation code: ______.
7. Restart Ingres: Attempt once again to start up the installation by issuing the following command at the operating system prompt:
ingstart