|
|
|
The UNIX operating system has various trace facilities that are useful in troubleshooting Ingres.
|
|
|
Invoking a Bourne shell with the -x option causes each shell command to be printed before it is executed. This is especially useful for diagnosing problems with installation shell scripts.
To use this trace on the Ingres shutdown script, call the Bourne shell (or Korn shell) with the -x option, passing the name ingstop as the script to be executed:
sh -x ingstop
This option can only be used with UNIX shell scripts, not with binary executables.
If you are in doubt as to whether a program or command is a binary or shell script, type:
file program_name
UNIX replies with "commands text," "ASCII text," or "executable shell script" if it is an executable shell script. Otherwise the file command returns a message specific to your machine—something like demand paged executable and possibly the designated chip on which it was compiled to run.
|
|
|
Some UNIX platforms (such as Sun) provide a facility to trace system calls as they are made by a process. To invoke it, enter trace at the operating system prompt.
|
|
|
To ensure that any new errors written to the Ingres error log file are displayed on the terminal screen, issue the following command at the terminal.
tail -f $II_SYSTEM/ingres/files/errlog.log
To continuously monitor the activities of the Ingres recovery process (dmfrcp), issue this command:
tail -f $II_SYSTEM/ingres/files/iircp.log