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
Ingbuild on UNIX
The executable script ingbuild performs all the steps necessary to set up an installation. It checks system resources, installs shared memory and semaphores, configures DBMS server parameters, configures the logging and locking system, and starts all the required processes.
The ingbuild program is located in $II_SYSTEM/ingres/utility. It makes use of numerous shell commands as well as the following Ingres binary and shell executables:
• createdb
• iilink
• ingstop
• ingstart
• ingprenv
• ingunset
• sql
One of the last things ingbuild does is call the ingstart
script to start installation processes. When ingstart
is called, it displays the message “Starting the Name Server process (iigcn).” If there are startup problems after this message has displayed, see
Detect Ingres Startup Problems on UNIX.
Before you can diagnose a problem with ingbuild, you must identify which subroutine is failing. If you know which routine is failing and it is ingstart or one of the main installation processes (iigcn, iigcc, II_IUSV_nnn, dmfacp or iidbms), see the section below that addresses that executable.
Details on tracing are described in
Bourne Shell -x Option.
Detect Ingres Startup Problems on UNIX
To diagnose Ingres problems, use the following procedure.
1. Display which processes are running by using the csreport and operating system ps commands.
2. Verify that all required Ingres system processes are running. The following processes (in the order they are started) are the minimum required for a complete installation:
iigcn
Name Server process
iigcc
Communications Server process (present only on sites with Ingres Net)
iidbms (II_IUSV_nnn)
Recovery Server process
iigcd
Data Access Server process
dmfacp
Archiver process
iidbms
DBMS Server process
iislave
DBMS Server asynchronous write daemons—these processes are created at the time of the first database write operation (only present on sites where Ingres does not use OS threads or asynchronous I/O)
iistar
Star Server process (present only on sites with Ingres Star)
iigcb
Bridge Server process (present only on sites with Ingres Bridge)
Note: If the command ingprenv | grep II_CLIENT shows “II_CLIENT = true”, you need to run only the Name Server and Communications Server processes.
In a few special cases Ingres can be run without the Communications Server process. This includes releases that use the streams device driver for interprocess communications. If you are not sure if your release uses the streams device driver, see your Readme file.
3. If ingstart does not complete successfully, try to identify the reason for startup failure. For example:
The problem is with ingstart. The ingstart script fails due to results of the checks it makes for sufficient resources and installation settings. If this is the reason for startup failure, correct the deficiency.
A process failed to start. If a process failed to start, continue on to the details sections on startup problems for that specific process.