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:

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 Startup Problems on UNIX (see page 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 (see page Bourne Shell -x Option).