05-05-2013
Quote:
Originally Posted by
MichaelFelt
This would depend on what you are trying to collect.
One, classic approach, might be to use sar perhaps.
A different approach would be to use AIX Advanced Accounting.
If you are looking for a deep approach, and are looking at a specific process (rather than all processes) of a know PID and/or TID you could use various trace based tools (e.g., tprof, curt, etc) and/or trace and trcrpt. Rather than PID this could also be command name - there are too many options to name them all.
And, another option could be using probevue mechanism.
Hope this helps!
Hello,
Thank you for your answers. I should have specify my working environment :
Business app : SAP R3 on Oracle Cluster-ware
DB : Oracle 11g + RAC
FS : GPFS
OS : AIX 6.1
Servers : IBM psystem (Power7 CPU)
We are investigating divergence between real CPU consumption versus 'sap + rac oracle + gpfs' benchmarks in order to challenge our advanced support from SAP and Oracle.
By the way, I am not a AIX sysadmin neither I am an AIX expert. And unfortunately, I do not have hands over the system. To do something on the system, I have to ask our contractor in charge of. However, I understand thing well ... I think
About your propositions :
First thing first, I want just graph this waiting time over the time no matter the process. I should read more carefully the SAR doc. I didn't know about the AIX advanced accouting system. Hence, I printed the doc and now I have to read it
If we find something particuliar, I may go for a deep analysis but not with a real time trace I that is possible. We ran some CURT (3 time 1 minutes) and heavily impacted our 6000 users :x
Thank you again for your time. I will be certainly back with others questions and I hope results.
Regards
9 More Discussions You Might Find Interesting
1. HP-UX
Gurus,
Having a GS1280 box with OSF1 v5.1 installed (16 processors), the run queue value from the vmstat command reports a very high value (about 25 to 30). Does this reflect a CPU bound system. Note that the average CPU utilization is about 60 % which means that the CPU is not that loaded.
Can... (0 Replies)
Discussion started by: Negm
0 Replies
2. AIX
Hi all,
I am trying to find out the process wait time on Unix(AIX/SOLARIS) machine( only sh/ksh/csh):
Like
EXAMPLE 1 :
$ vmstat 2
System configuration: lcpu=16 mem=32000MB
kthr memory page faults cpu
----- -----------... (4 Replies)
Discussion started by: chandrakala.sg
4 Replies
3. UNIX for Dummies Questions & Answers
Im using the vmstat command to display the CPU run queue, but i want to put that into a program so is there a way to just display the number under the r?
Thanks, (1 Reply)
Discussion started by: RAFC_99
1 Replies
4. UNIX for Advanced & Expert Users
I am working on an application with some rather interesting build performance issues. If we build on Solaris/Linux x86/AMD64 the build is rather fast, but it takes more than five times as long on our Solaris Sparc servers (single-threaded builds on the workstations, but multi-threaded on the... (5 Replies)
Discussion started by: Elric of Grans
5 Replies
5. Shell Programming and Scripting
I have no idea why this job has been put into waiting state by server. Can anyone help me to run this job from waiting state.
ps -elf | grep 'usr_script'
4 S usr_script 3929 3926 0 77 0 - 2976 wait Oct21 ? 00:00:00 /bin/ksh /application_folder/script/report
0 S usr_script ... (2 Replies)
Discussion started by: zooby
2 Replies
6. Linux
Hi,
Am doing an enhancements related to monitoring a Linux disk I/O statistics.
The /proc/diskstats file is used to get the each disk I/O statistics. But, It returns the raw value.
How to calculate the Disk Queue Length and Disk Busy time from the raw values.
Guide me. (1 Reply)
Discussion started by: maruthu
1 Replies
7. Shell Programming and Scripting
Hello,
I am running GNU bash, version 3.2.39(1)-release (x86_64-pc-linux-gnu). I have a specific question pertaining to waiting on jobs run in sub-shells, based on the max number of parallel processes I want to allow, and then wait... (1 Reply)
Discussion started by: srao
1 Replies
8. UNIX for Advanced & Expert Users
Hi Everybody,
Can anybody explain how CPU idle% is about 50%, but runq-sz more than 1?
sar from Solaris 10:
00:00:05 %usr %sys %wio %idle
17:00:08 27 12 0 61
17:20:05 40 15 0 45
17:40:05 27 12 0 61
18:00:05 23... (2 Replies)
Discussion started by: sant
2 Replies
9. Solaris
Hi
I have a system running solaris 10, and I intend to use a NetApp as its storage system. The application requires a throughput between the server and the storage 7000 disk IOPS (random IO sustained throughput with response time of 20 mili second and 16k block size).
How to make sure that I... (6 Replies)
Discussion started by: fretagi
6 Replies
LEARN ABOUT SUSE
ocf_heartbeat_oracle
OCF_HEARTBEAT_ORACLE(7) OCF resource agents OCF_HEARTBEAT_ORACLE(7)
NAME
ocf_heartbeat_oracle - Manages an Oracle Database instance
SYNOPSIS
oracle [start | stop | status | monitor | validate-all | methods | meta-data]
DESCRIPTION
Resource script for oracle. Manages an Oracle Database instance as an HA resource.
SUPPORTED PARAMETERS
sid
The Oracle SID (aka ORACLE_SID). (required, string, no default)
home
The Oracle home directory (aka ORACLE_HOME). If not specified, then the SID along with its home should be listed in /etc/oratab.
(optional, string, no default)
user
The Oracle owner (aka ORACLE_OWNER). If not specified, then it is set to the owner of file $ORACLE_HOME/dbs/*${ORACLE_SID}.ora. If this
does not work for you, just set it explicitely. (optional, string, no default)
ipcrm
Sometimes IPC objects (shared memory segments and semaphores) belonging to an Oracle instance might be left behind which prevents the
instance from starting. It is not easy to figure out which shared segments belong to which instance, in particular when more instances
are running as same user. What we use here is the "oradebug" feature and its "ipc" trace utility. It is not optimal to parse the
debugging information, but I am not aware of any other way to find out about the IPC information. In case the format or wording of the
trace report changes, parsing might fail. There are some precautions, however, to prevent stepping on other peoples toes. There is also
a dumpinstipc option which will make us print the IPC objects which belong to the instance. Use it to see if we parse the trace file
correctly. Three settings are possible: - none: don't mess with IPC and hope for the best (beware: you'll probably be out of luck,
sooner or later) - instance: try to figure out the IPC stuff which belongs to the instance and remove only those (default; should be
safe) - orauser: remove all IPC belonging to the user which runs the instance (don't use this if you run more than one instance as same
user or if other apps running as this user use IPC) The default setting "instance" should be safe to use, but in that case we cannot
guarantee that the instance will start. In case IPC objects were already left around, because, for instance, someone mercilessly
killing Oracle processes, there is no way any more to find out which IPC objects should be removed. In that case, human intervention is
necessary, and probably _all_ instances running as same user will have to be stopped. The third setting, "orauser", guarantees IPC
objects removal, but it does that based only on IPC objects ownership, so you should use that only if every instance runs as separate
user. Please report any problems. Suggestions/fixes welcome. (optional, string, default instance)
clear_backupmode
The clear of the backup mode of ORACLE. (optional, boolean, default false)
shutdown_method
How to stop Oracle is a matter of taste it seems. The default method ("checkpoint/abort") is: alter system checkpoint; shutdown abort;
This should be the fastest safe way bring the instance down. If you find "shutdown abort" distasteful, set this attribute to
"immediate" in which case we will shutdown immediate; If you still think that there's even better way to shutdown an Oracle instance we
are willing to listen. (optional, string, default checkpoint/abort)
SUPPORTED ACTIONS
This resource agent supports the following actions (operations):
start
Starts the resource. Suggested minimum timeout: 120.
stop
Stops the resource. Suggested minimum timeout: 120.
status
Performs a status check. Suggested minimum timeout: 5.
monitor
Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 120.
validate-all
Performs a validation of the resource configuration. Suggested minimum timeout: 5.
methods
Suggested minimum timeout: 5.
meta-data
Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.
EXAMPLE
The following is an example configuration for a oracle resource using the crm(8) shell:
primitive example_oracle ocf:heartbeat:oracle
params
sid=string
op monitor depth="0" timeout="30" interval="120"
SEE ALSO
http://www.linux-ha.org/wiki/oracle_(resource_agent)
AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors)
resource-agents 1.0.3 07/05/2010 OCF_HEARTBEAT_ORACLE(7)