Sponsored Content
Full Discussion: Excessive Paging&Swapping!
Top Forums UNIX for Advanced & Expert Users Excessive Paging&Swapping! Post 34888 by sssow on Wednesday 19th of March 2003 06:41:24 PM
Old 03-19-2003
Amit
The default sizes of the rollback segments and redo logs are very small. Do you have all these tablespaces on single disk. Use system tools like iostat etc. and locate which is causing the excessive IO. Also you can use oracle tracing and tkprof tool to estimate the statistics of the database operations. This will give you the details of CPU time, disk usage, indexing issues if any
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

paging space & monitor

Hi folks, Lately my RS 6000 server is giving some problems. Needs a reboot from time to time (4-8 days):mad: Specs: IBM/RS6000 Unix 4.3 3 gigabyte memory I keep getting messages like : " The fork function failed " I have raised the paging space from 1 gigabyte to 3 gigabyte,... (2 Replies)
Discussion started by: Erik Rooijmans
2 Replies

2. Filesystems, Disks and Memory

Paging and Swapping

Hi Guys: Would like to know how to check system swapping and paging and some theory on how they function. I am an oracle dba and my environment is 8171 on AIX 433. We have a 1GB of RAM on the box and I am educating myself to see how much more SGA can be accommodated on the box and what are the... (2 Replies)
Discussion started by: ST2000
2 Replies

3. UNIX for Dummies Questions & Answers

excessive IOWAIT

i have a server constantly have high iowait, but i am not able to tell which process generate the most of io. none commands, such as iostat, sar, top will give me this kind of information. hope there is some command can help me to spot the process generate the most of io let to know input... (1 Reply)
Discussion started by: giantpanda77
1 Replies

4. AIX

Excessive Page INs

Gurus, What does excessive Page Ins indicate for the memory status on the machine. Or, in another form, Reardless the OS, does excessive Page INs reflects memory shortage ? (6 Replies)
Discussion started by: Negm
6 Replies

5. UNIX for Advanced & Expert Users

virtual memory management, swapping paging

can anybody explain me the concepts virtual memory mangement, swapping and paging? although i roughly know what they are , i need more solid distinction between them, and also i want to figure out the relations between them? do you have any well-defined definitons for this concepts? (2 Replies)
Discussion started by: gfhgfnhhn
2 Replies

6. AIX

Why using "%" of Paging size increases & how to decrease this percentage?

Hi I have found a problem on my AIX 5.1 server. day by day the paging size is increasing,what is the reason behind it and if percentage is at 100 what will happen. Oracle 9i is running on my server. PAGING SPACE size,mb 5632 % used 14.6 % free 85.3 How can i decrease the using... (6 Replies)
Discussion started by: dearsumon
6 Replies

7. AIX

Excessive interrupt disablement time

Has anyone seen this error before? On the IBM website they suggest updating to AIX 6.1.0.0 TL2, but we are already at that level. Any help or suggestions are appreciated! Thanks! />errpt -a --------------------------------------------------------------------------- LABEL: ... (2 Replies)
Discussion started by: troym72
2 Replies

8. UNIX for Dummies Questions & Answers

AIX & DB2 paging issues

AIX & DB2 paging issues Hello I needs some help on AIX & DB2 paging issues. Recently a db2 query caused paging issues which then lead to memory problems and a server restart. Is there anyway of finding out what db2 queries were causing the problem.. Thanks in advance (2 Replies)
Discussion started by: nedkao
2 Replies

9. Solaris

Sol10 + OpenLDAP = excessive logging & full file system??!!

Hello all, new to this forum (member of many others). Hopefully I can find help here. SERVER: Brand new server Oracle Enterprise SPARC T4-1 Loaded Solaris SPARC 10 u10, patched to 147440-27 Loaded OpenLDAP v2.4.30 Loaded Berkley DB 4.7.25.NC Loaded OpenSSL 1.0.1c Note: All packages are... (2 Replies)
Discussion started by: Wraith_G2IC
2 Replies

10. Solaris

Monitoring Paging and Swapping

Hi all, This might sound silly but i am trying to determine if i have sufficient memory or not. My definition of sufficient memory = no swapping + no paging to physical swap file. I know i can use vmstat to monitor swapping and paging and using the SR column as well. But wouldn't it be... (28 Replies)
Discussion started by: javanoob
28 Replies
SA(8)							    BSD System Manager's Manual 						     SA(8)

NAME
sa -- print system accounting statistics SYNOPSIS
sa [-abcdDfijkKlmnqrstu] [-P file] [-U file] [-v cutoff] [file ...] DESCRIPTION
The sa utility reports on, cleans up, and generally maintains system accounting files. The sa utility is able to condense the information in /var/account/acct into the summary files /var/account/savacct and /var/account/usracct, which contain system statistics according to command name and login id, respectively. This condensation is desirable because on a large sys- tem, /var/account/acct can grow by hundreds of blocks per day. The summary files are normally read before the accounting file, so that reports include all available information. If file names are supplied, they are read instead of /var/account/acct. After each file is read, if the summary files are being updated, an updated summary will be saved to disk. Only one report is printed, after the last file is processed. The labels used in the output indicate the following, except where otherwise specified by individual options: avio Average number of I/O operations per execution cp Sum of user and system time, in minutes cpu Same as cp k CPU-time averaged core usage, in 1k units k*sec CPU storage integral, in 1k-core seconds re Real time, in minutes s System time, in minutes tio Total number of I/O operations u User time, in minutes The options to sa are: -a List all command names, including those containing unprintable characters and those used only once. By default, sa places all names containing unprintable characters and those used only once under the name ``***other''. -b If printing command statistics, sort output by the sum of user and system time divided by number of calls. -c In addition to the number of calls and the user, system and real times for each command, print their percentage of the total over all commands. -d If printing command statistics, sort by the average number of disk I/O operations. If printing user statistics, print the average number of disk I/O operations per user. -D If printing command statistics, sort and print by the total number of disk I/O operations. -f Force no interactive threshold comparison with the -v option. -i Do not read in the summary files. -j Instead of the total minutes per category, give seconds per call. -k If printing command statistics, sort by the cpu-time average memory usage. If printing user statistics, print the cpu-time average memory usage. -K If printing command statistics, print and sort by the cpu-storage integral. -l Separate system and user time; normally they are combined. -m Print per-user statistics rather than per-command statistics. -n Sort by number of calls. -P file Use the specified file for accessing the per-command accounting summary database, instead of the default /var/account/savacct. -q Create no output other than error messages. -r Reverse order of sort. -s Truncate the accounting files when done and merge their data into the summary files. -t For each command, report the ratio of real time to the sum of user and system cpu times. If the cpu time is too small to report, ``*ignore*'' appears in this field. -U file Use the specified file for accessing the per-user accounting summary database, instead of the default /var/account/usracct. -u Superseding all other flags, for each entry in the accounting file, print the user ID, total seconds of cpu usage, total memory usage, number of I/O operations performed, and command name. -v cutoff For each command used cutoff times or fewer, print the command name and await a reply from the terminal. If the reply begins with ``y'', add the command to the category ``**junk**''. This flag is used to strip garbage from the report. By default, per-command statistics will be printed. The number of calls, the total elapsed time in minutes, total cpu and user time in min- utes, average number of I/O operations, and CPU-time averaged core usage will be printed. If the -m option is specified, per-user statistics will be printed, including the user name, the number of commands invoked, total cpu time used (in minutes), total number of I/O operations, and CPU storage integral for each user. If the -u option is specified, the uid, user and system time (in seconds), CPU storage integral, I/O usage, and command name will be printed for each entry in the accounting data file. If the -u flag is specified, all flags other than -q are ignored. If the -m flag is specified, only the -b, -d, -i, -k, -q, and -s flags are honored. FILES
/var/account/acct raw accounting data file /var/account/savacct per-command accounting summary database /var/account/usracct per-user accounting summary database EXIT STATUS
The sa utility exits 0 on success, and >0 if an error occurs. SEE ALSO
lastcomm(1), acct(5), ac(8), accton(8) AUTHORS
Chris G. Demetriou <cgd@postgres.berkeley.edu> CAVEATS
While the behavior of the options in this version of sa was modeled after the original version, there are some intentional differences and undoubtedly some unintentional ones as well. In particular, the -q option has been added, and the -m option now understands more options than it used to. The formats of the summary files created by this version of sa are very different from the those used by the original version. This is not considered a problem, however, because the accounting record format has changed as well (since user ids are now 32 bits). BUGS
The number of options to this program is absurd, especially considering that there is not much logic behind their lettering. The field labels should be more consistent. The VM system does not record the CPU storage integral. BSD
May 18, 2007 BSD
All times are GMT -4. The time now is 05:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy