Tools for Identifying Operating System Problems
The following tools can help you identify operating system resource problems:
• Review the minimum requirements for a basic Ingres installation given in the Readme file. If your particular environment requires more resources, use the Ingres utilities to verify that there are enough resources.
UNIX:
BSD:
pstat utility--to display the status of UNIX system tables and system swap space
vmstat utility--to display virtual memory status
System V:
• sar utility--to display activity of various system resources such as CPU utilization, swapping activity, and disk activity.
• show memory--displays the system memory resources and the amount of non-paged dynamic memory (total, free and in use).
• show process/id=pid/continuous--displays the amount of page faulting, working set, buffered I/O, and direct I/O the server is doing.
• show device--indicates if a particular disk drive is out of disk space.
• show device /files--if there is a problem starting an installation, this command can be used to make sure that an Ingres process is not holding on to a mailbox.
The installation utility allows the examination of all Ingres installed images, showing the amount of global pages and sections available and used.
VMS:
The following VMS tools are very useful for tracing script problems:
• set verify--allows you to see the commands used in the installation script or any other VMS command procedure.
• set watch file/class=major (requires CMEXEC VMS privilege)--allows all the files that are being accessed to be displayed. This assists in diagnosing if a location of a file or library is being incorrectly referenced. Use this command when debugging Ingres processes interactively.
• The displays can be turned off with the following command entered at the operating system prompt:
Important! This is an unsupported VMS command. Use at your own risk.
set watch file/class=none.