|
|
|
Many operating systems provide utilities to administer and troubleshoot. Most of the operating systems provide context sensitive help to use the tools.
|
|
|
You can use the following Windows operating system utilities to monitor Ingres:
For a full description of the Windows utilities, see your Windows documentation.
|
|
|
The Windows Diagnostics program can help you determine your operating system's configuration. This tool can be found in Settings, Control Panel, Administrative Tools, Computer Management.
|
|
|
Performance Monitor is a Windows graphical tool for measuring the performance of your own computer or other computers on a network. On each computer, you can view the behavior of objects such as processors, memory, cache, threads, and processes. Each of these objects has an associated set of counters that provide information on such things as device usage, queue lengths, and delays, as well as information used for throughput and internal congestion measurements.
It provides charting, alerting, and reporting capabilities that reflect current activity along with ongoing logging. You can also open log files at a later time for browsing and charting as if they were reflecting current activity. To monitor performance on Windows, see the operating system documentation.
|
|
|
Event Viewer is a tool for monitoring events in your system. You can use Event Viewer to view and manage System, Security, and Application event logs. To access the Event Viewer, right-click on the My Computer icon and select Manage. The Computer Management Window is displayed. The Event Viewer is available under the System Tools.
|
|
|
This program can be used to view the system configuration and environment. For a description of how the information is presented and the capabilities of the utility, see the online help.
|
|
|
To start the Registry Editor, run REGEDT32.EXE from File Manager or Program Manager, or type start REGEDT32 in a command window. The Registry Editor program has a similar view to the File Manager program.
|
|
|
The Task Manager enables you to monitor and control your computer and what is running on it. It shows you programs and processes that are running as well as performance. To access the Task Manager, right click an empty area in the task bar and click Task Manager.
|
|
|
You can use the following UNIX operating system utilities to monitor Ingres:
For a full description of the UNIX options, see your UNIX documentation (or online help). A detailed description of the utilities can be found in the Command Reference Guide.
Note: Not all of the utilities are present on every UNIX system. Some are present only in a BSD or System V environment but not both.
|
|
|
This command provides virtual memory and cpu information on each active process submitted from your account. Here is a sample ps output:
PID TT STAT TIME SL RE PAGEIN SIZE RSS LIM %CPU %MEM COMMAND
xx06 p3 s 28:50 13 99 45886 3696 2856 xx 0.0 39.3 iidbms
xx94 p3 s 4:24 0 99 2899 720 344 xx 0.0 4.7 dmfrcp
xx09 p3 I 0.51 99 99 4488 4 184 xx 0.0 2.5 iislave
xx19 p3 I 0.57 99 99 5764 64 17 xx 0.0 2.4 iislave
xx96 p3 I 0.04 99 99 1852 696 160 xx 0.0 2.2 dmfacp
The display fields are as follows:
Field |
Description |
|---|---|
PID |
Process ID field |
TT |
Controlling terminal |
STAT |
Process status Runnability of the process: Runnable (r), Stopped (t), Disk or other short-term wait (d), Sleeping (s), or Idle (i) Swap status: Swapped out (w) or Loaded in core (blank) Process priority change: Reduced (n), Increased (>) or No change (blank) |
SL |
Sleep time (seconds blocked) |
RE |
Residency time (seconds in core) |
PAGEIN |
Number of disk I/Os resulting from page references not in core |
SIZE |
Virtual process size |
RSS |
Resident set size |
LIM |
Soft memory limit (setrlimit), else "xx" |
%CPU |
CPU utilization (1 minute decaying average) |
%MEM |
Memory utilization |
COMMAND |
Process name |
|
|
|
The iostat command returns information about I/O status. It lists statistics on current I/O activity for each disk device and system CPU utilization percentages. Here is a sample iostat output:
tty cpu
tin tout us ni sy id
1 18 19 0 3 78
/dev/*dsk/c0d*s*/dev/*dsk/cld*s*/dev/*dsk/c2d*s*/dev/*dsk/c4d*s*
bps sps msps bps sps msps bps sps msps bps sps msps
2 0.1 61.7 1 0.0 95.5 1 0.0 60.4 2 0.2 44.3
|
|
|
Print Statistics utility is useful for examining system tables and system swap space.
The command /etc/pstat –s, shows system swap space activity. An example output:
589944 used, 667364 free, 61864 wasted
avail (num*size): 316*2048 5*1024 6*512 13*256 21*128 38*64 54*32
Note: For a description of the output units, see your operating system guide or online MAN pages. On some machines output is in bytes (as in this example). On others it is in units equal to the machine's page size.
The command /etc/pstat -T gives a list of used and free slots in various system tables. Here is a sample output:
1717/3216 files
937/2384 inodes
333/1300 processes
266/325 mfiles
595176/1256780 swap
The pstat utility can be used to give other useful information if the user has knowledge of the UNIX kernel. It can tell you, for example, the state of a running process, which files are open, which operating system locks apply and which processes have which files open.
|
|
|
The sar (System Activity Reporter) command can be used to list CPU utilization statistics, disk and swapping activity, and other status options. The UNIX sar command samples cumulative activity counters in the operating system and reports on various system activities. Just a few of the reports available that are of use for the system administrator are CPU utilization, disk activity, and swapping activity. See examples below.
There are many other options available, including reports on unused memory pages and disk blocks (swap space), and message and semaphore activity. For the system administrator, sar is an indispensable tool.
06:38:26 %usr %sys %wio %idle
06:38:31 1 3 96 0
This output shows the portion of CPU time spent running in user mode, system mode, idle with some process waiting for block I/O, or otherwise idle.
06:39:53 device %busy avque r+w /s blks/s avwait avserv
06:39:53 disc0-0 16 13.6 6 17 349.6 29.7
disc0-5 0 1.0 0 2 0.0 20.0
The display shows the portion of time the device was busy servicing requests (%busy), the average number of outstanding requests (avque), the number of data transfers (r+w/s), the number of bytes transferred in 512-byte units (blk/s), the average time in milliseconds that requests wait idly on queue (avwait), and the average time for requests to be serviced (avserve).
06:40:45 swpin/s bswin/s swpot/s bswot/s pswch/s
06:40:50 0.00 0.0 0.00 0.0 19
The fields swpin/s, swpot/s are the number of swap transfers. The fields bswin/s, bswot/s are the number of 512-byte units transferred in/out. The field pswch/s is the number of process switches.
|
|
|
The /etc/sysdef (System Definition) command (implemented only on some System V operating systems) displays a list of all tunable kernel parameters and their configuration in the currently active kernel. Here is a sample sysdef output:
Tunable Kernel Parameters:
250 buffers in buffer cache (NBUF)
30 entries in callout table (NCALL)
150 inodes (NINODE)
150 s5inodes (NS5INODE)
150 entries in file table (NFILE)
25 entries in mount table (NMOUNT)
100 entries in proc table (NPROC)
210 entries in shared region table (NREGION)
120 clist buffers (NCLIST)
25 processes per user id (MAXUP)
64 hash slots for buffer cache (NHBUF)
20 buffers for physical I/O (NPBUF)
50 size of system virtual space map (SPTMAP)
16 fraction of memory for vhandlow (VHNDFRAC)
0 maximum physical memory to use (MAXPMEM)
10 auto update time limit in seconds (NAUTOUP)
60 maximum number of open files per process (NOFILES)
256 number of streams queues (NQUEUE)
48 number of streams head structures (NSTREAM)
4 number of 4096 bytes stream buffers (NBLK4096)
32 number of 2048 bytes stream buffers (NBLK2048)
32 number of 1024 bytes stream buffers (NBLK1024)
32 number of 512 bytes stream buffers (NBLK512)
64 number of 256 bytes stream buffers (NBLK256)
128 number of 128 bytes stream buffers (NBLK128)
256 number of 64 bytes stream buffers (NBLK64)
256 number of 16 bytes stream buffers (NBLK16)
128 number of 4 bytes stream buffers (NBLK4)
2560 maximum size of user's virtual address space in pages (MAXUMEM)
2560 for package compatibility equal to MAXUMEM (MAXMEM)
25 page stealing low water mark (GPGSLO)
40 page stealing high water mark (GPGSHI)
9 page aging interval (AGEINTERVAL)
1 bdflush run rate (BDFLUSHR)
25 minimum resident memory for avoiding deadlock (MINARMEM)
25 minimum swappable memory for avoiding deadlock (MINASMEM)
1 maximum number of pages swapped out (MAXSC)
1 maximum number of pages saved (MAXFC)
*
* Utsname Tunables
*
3.2 release (REL)
chipmunk node name (NODE)
chipmunk system name (SYS)
2 version (VER)
*
* Streams Tunables
*
87 number of multiplexor links (NMUXLINK)
9 maximum number of pushes allowed (NSTRPUSH)
256 initial number of stream event calls (NSTREVENT)
1 page limit for event cell allocation (MAXSEPGCNT)
4096 maximum stream message size (STRMSGSZ)
1024 max size of ctl part of message (STRCTLSZ)
80 max low priority block usage (STRLOFRAC)
90 max medium priority block usage (STRMEDFRAC)
*
* RFS Tunables
*
10 entries in server mount table (NSRMOUNT)
*
* IPC Messages
*
100 entries in msg map (MSGMAP)
2048 max message size (MSGMAX)
4096 max bytes on queue (MSGMNB)
50 message queue identifiers (MSGMNI)
8 message segment size (MSGSSZ)
40 system message headers (MSGTQL)
1024 message segments (MSGSEG)
*
* IPC Semaphores
*
10 entries in semaphore map (SEMMAP)
10 semaphore identifiers (SEMMNI)
60 semaphores in system (SEMMNS)
30 undo structures in system (SEMMNU)
25 max semaphores per id (SEMMSL)
10 max operations per semop call (SEMOPM)
10 max undo entries per process (SEMUME)
32767 semaphore maximum value (SEMVMX)
16384 adjust on exit max value (SEMAEM)
*
* IPC Shared Memory
*
1048576 max shared memory segment size (SHMMAX)
1 min shared memory segment size (SHMMIN)
100 shared memory identifiers (SHMMNI)
6 max attached shm segments per process (SHMSEG)
512 max in use shared memory (SHMALL)
*
* File and Record Locking
*
100 records configured on system (FLCKREC)
|
|
|
The vmstat (Virtual Memory Statistics) command returns virtual memory status information, including process states and paging activity. Here is a sample vmstat output:
procs memory page disk faults cpu
r b w avm fre di re rd pi po de z0 z1 z2 z3 in sy cs us sy id
1 0 0 2536 456 24 2 1 4 0 0 1 1 0 1 24 475 23 4 6 91
0 0 0 2748 356 24 0 0 0 0 0 2 0 0 3 26 323 29 1 5 95
0 0 0 1044 344 24 0 0 0 0 0 0 0 0 0 16 216 18 0 3 97
0 0 0 2288 344 24 0 0 0 0 0 0 0 0 0 19 334 27 1 4 95
1 0 0 2372 332 24 0 0 4 0 0 0 0 0 1 28 552 40 1 6 93
The procs columns define the process states: in run queue (r), blocked for resources (b), and runnable or short sleeper (w).
The memory columns show virtual and real memory status: avm is active virtual pages (belonging to processes active in approximately the last 20 seconds), fre is size of the free list, and di is the number of dirty pages.
The page columns show page faults and paging activity. These are expressed in units per second, averaged over 5 seconds: re are page reclaims, rd are page reclaims from the dirty list, and pi, po are pages paged in/out. The de field is anticipated short-term memory shortfall.
The disk columns list disk activity, showing the device name and operations per second.
|
|
|
VMS utilities vary depending on the operating system release. For detailed information on utilities supported by your system, see your operating system guides (or online help).
|
|
|
The VMS online help facility (help) provides information on the specified command. The syntax is help command.
|
|
|
The VMS monitor utility returns dynamic information about VMS system performance for a specified component. Some of the most useful components to monitor are:
|
|
|
The VMS show utility returns process and other VMS system status information on a specified component. Qualifiers (/qualifier) are used on certain components, as shown in the examples that follow. Some useful forms of the VMS show command appear in the following list.
date and time stamp
process ID number
process name and identification with UIC
processing state
priority
total process I/O
cumulative cpu time used
cumulative page faults
amount of physical memory being used
type of process
VAX/VMS V6.0 on node FOO 9-FEB-2001 09:34:17.48 Uptime 13 13:46:12
Pid Process Name State Pri I/O CPU Page flts Ph.Mem
00205374 DMFRCPBE HIB 6 6270 0 00:00:15.71 2756 4280
00202F75 DMFACPBE HIB 5 934 0 00:00:57.09 1115 2302
00204376 II_GCNBE HIB 6 667 0 00:00:03.15 782 1363
00202B77 II_GCC_BE_2B77 HIB 5 142 0 00:00:02.15 664 1549
00205578 II_DBMS_BE_5578 HIB 5 38540 0 00:04:31.58 9390 13903
002002C3 DMFCSPBE HIB 5 71071 0 00:00:22.27 399 173
date and time stamp
process terminal
user name and UIC
node name
process name and process identification
priority
default directory
allocated devices
Some of the show process qualifiers you can use are:
/memory—displays the process' use of dynamic memory areas. This qualifier is allowed only for the current process.
/quotas—displays, for each resource, a quota or a limit. The quota values reflect any quota reductions resulting from subprocess creation. Limit values reflect the resources available to a process at creation.
/priv—displays current privileges for the process.
/all—selects all configured processors, active or inactive, as the subject of the display.
/full—produces information from the summary display and also lists the current CPU state, current process (if any), revision levels, and capabilities for each configured processor. The display indicates which processes can execute only on certain processors in the configuration.
/allocate—displays all devices currently allocated to processes.
/file—shows all open files on the device, together with the process name and the process ID that opened the file.
/mounted—displays all devices currently having volumes mounted.
II_SYSTEM:[INGRES.UTILITY]INGSYSDEF.COM – Defines Ingres system administration, DBA, and user symbols.
II_SYSTEM:[INGRES.UTILITY]INGDBADEF.COM – Defines Ingres DBA and user symbols.
II_SYSTEM:[INGRES.UTILITY]INGUSRDEF.COM – Defines Ingres user symbols.
|
|
|
The VMS sysgen utilitty displays system configuration parameters. To run this utility, execute the following command at the operating system prompt:
run sys$system:sysgen
For a full description of the system definitions, see your VMS System manual.
|
|
|
Many vendors also provide monitor utilities. These often present a more user-friendly interface than the generic utilities mentioned above. Check your operating system documentation for availability of these useful vendor-specific utilities.