11-25-2012
then i must consider that a normal activity, or i can configure the system to have minimum page faults?
you said that file caching is easy, can you explain better and eventually where i can find documentation that focus on this?
Thank you so much
p.s. i have opened a case with ibm/oracle and no one cannot solve/explain this problem..
10 More Discussions You Might Find Interesting
1. HP-UX
Hello
Please can you tell me how to access COPY ON WRITE page faults in HP -UNIX.
I found the structure in
/usr/include/sys/vmmeter with the structure name vmmeter.
Please tell me the function to fill the values to this structure and also
the arguments for function.:: (5 Replies)
Discussion started by: manjunath
5 Replies
2. HP-UX
Hi,
Will anybody tell me what is this 'intransient blocking page faults' in HP-UX, it is in the structure _pst_vminfo in the header file /ust/include/sys/pstat/vm_pstat_body.h? (4 Replies)
Discussion started by: sushaga
4 Replies
3. AIX
Sorry my poor english
In 570 pseries nmon shows excessive page faults, ascents of something more than 30000 Page faults.
System: AIX 5.2 ML5
Processor Type: PowerPC_POWER5
Number Of Processors: 2
Processor Clock Speed: 1656 MHz
CPU Type: 64-bit
Kernel Type: 64-bit
Memory Size: 2816 MB
... (1 Reply)
Discussion started by: daviguez
1 Replies
4. Solaris
Hi,
We are running SUN sparc 5.8, notice frequent "Page Faults" message from our monitor s/w "ServerVantage" coming but no message display in SUN syslog or messages log. Any ideas why or what to check?
thanks,
Ahmad (2 Replies)
Discussion started by: Ahmad
2 Replies
5. Solaris
Hi,
Currently I'm experience very high page ins on my system running on solaris 10.
From vmstat, the page ins figure is very high, further drill down shows the page ins are from file system and occassional spike in executable page ins.
Details as follow:
oracle@perch:/files>> vmstat 5... (9 Replies)
Discussion started by: srage
9 Replies
6. AIX
Hello,
I've been reading your forums for quite a while and the great amount of information I find here always come in hand.This time however, I need some specific help...
I have a doubt with an AIX server which I'm failing to understand as I'm new to its concept of memory management...
... (8 Replies)
Discussion started by: flpgdt
8 Replies
7. AIX
Hi,
OS = AIX 5.3
Large number of page faults recently start to occure on AIX 5.3 lpar with mysql database installed. I need help in setting AIX OS parameter to solve the paging problem and some guidance on interpreting my stats
t
Code:
# vmstat... (5 Replies)
Discussion started by: crosys
5 Replies
8. AIX
Hi,
Can someone help and give the answer for the following questions:
1. When PowerHA SystemMirror 7.1 is installed on AIX 7.1, what RSCT component does Cluster Aware AIX (CAA) replace?
A. Group Services
B. Resource Manager
C. Topology Services
D. Resource Monitoring and Control... (2 Replies)
Discussion started by: walterchang100
2 Replies
9. Solaris
Hi guys,
I have a zone on a M5000 server running solaris 10. The zone has an SAP application running on it and facing some performance issues. As part of the troubleshooting, I've been recommended to look for any paging on the OS. Please advise how to look for the paging.
I've been looking at... (4 Replies)
Discussion started by: frum
4 Replies
10. UNIX for Beginners Questions & Answers
I am new to AIX but not new to unix.
I have an interview for an AIX systems admin position and I know they want someone who has knowledge of High Availability, Failover and LPARs
From my research so far, It appear powerha is used to setup high availability and failover on Power systems but is... (2 Replies)
Discussion started by: mathisecure
2 Replies
LEARN ABOUT ULTRIX
pfm_cleanup
pfm_cleanup(3ncs) pfm_cleanup(3ncs)
Name
pfm_cleanup - establish a clean-up handler
Syntax
#include <idl/c/base.h>
#include <idl/c/pfm.h>
status_$t pfm_$cleanup(cleanup_record)
pfm_$cleanup_rec *cleanup_record;
Arguments
cleanup_record A record of the context when is called. A program should treat this as an opaque data structure and not try to alter
or copy its contents. It is needed by and to restore the context of the calling process at the clean-up handler entry
point.
Description
The routine establishes a clean-up handler that is executed when a fault occurs. A clean-up handler is a piece of code executed before a
program exits when a signal is received by the process. The clean-up handler begins where is called; the routine registers an entry point
with the system where program execution resumes when a fault occurs. When a fault occurs, execution resumes after the most recent call to
There can be more than one clean-up handler in a program. Multiple clean-up handlers are executed consecutively on a last-in/first-out
basis, starting with the most recently established handler and ending with the first clean-up handler. The system provides a default
clean-up handler established at program invocation. The default clean-up handler is always called last, just before a program exits, and
releases any system resources still held, before returning control to the process that invoked the program.
Diagnostics
When called to establish a clean-up handler, returns the status pfm_$cleanup_set to indicate the clean-up handler was successfully estab-
lished. When the clean-up handler is entered in response to a fault signal, effectively returns the value of the fault that triggered the
handler.
This section lists status codes for errors returned by this routine in
pfm_$bad_rls_order Attempted to release a clean-up handler out of order.
pfm_$cleanup_not_found
There is no pending clean-up handler.
pfm_$cleanup_set A clean-up handler was established successfully.
pfm_$cleanup_set_signaledl
Attempted to use pfm_$cleanup_set as a signal.
pfm_$invalid_cleanup_rec
Passed an invalid clean-up record to a routine.
pfm_$no_space Cannot allocate storage for a clean-up handler. Clean-up handler code runs with asynchronous faults inhibited. When
returns something other than pfm_$cleanup_set indicating that a fault has occurred, there are four possible ways to
leave the clean-up code:
o The program can call to start the next clean-up handler with a different fault signal.
o The program can call to start the next clean-up handler with the same fault signal.
o The program can continue with the code following the clean-up handler. It should generally call to reenable
asynchronous faults. Execution continues from the end of the clean-up handler code; it does not resume where
the fault signal was received.
o The program can reestablish the handler by calling before proceeding.
Files
See Also
intro(3ncs), pfm_signal(3ncs)
pfm_cleanup(3ncs)