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.