Sponsored Content
Operating Systems AIX topas - computational memory 95% : Any Impact? Post 302492880 by panchpan on Tuesday 1st of February 2011 07:50:44 PM
Old 02-01-2011
Thank you very much zxmaus.

I am running AIX 5 and it has applications talking like tuxedo, websphere, oracle 11g.

a) Can you give me the URL where IBM recommends to have comp memory around 75%?
b) At what percentage of computational memory - Applications running on it or Server will crash? Or computational memory and paging space both can keep growing and things will hang/crash only when paging memory is around 90%. Basically trying to understand the importance of computational memory.

Thanks again!
 

7 More Discussions You Might Find Interesting

1. AIX

Memory usage statistic? (topas, nmon)

hi, how can i diplay: - the ammount RAM used /free - ammount of ram used from a pid or prozess we have the problem, that malloc is returing a NULL pointer errno = 12 ( not enough space). but i think there is still ram free. nmon : shows all memory used ? Memory Use Physical Virtual... (7 Replies)
Discussion started by: Lazzar
7 Replies

2. UNIX for Advanced & Expert Users

Need Help installing a Computational Tool Kit

Hi ! I have been trying to install IMSL Computational Tool Kit on a server. It is a Lunix Redhat V.4 with Intel pentium d processor and Intel fortran compiler 8.1 and the type of command shell we run is bash. I dont know if the problem is with the Installation or the Lunix system. I have... (1 Reply)
Discussion started by: dsmv
1 Replies

3. Cybersecurity

Computational complexity

This is a general question about the practical use of computational complexity in security. Wikipedia has a good article about the theoretical background of computational complexity. In the course of conversation with colleagues, a topic that is brought up occassionally is the security of any... (2 Replies)
Discussion started by: gratuitous_arp
2 Replies

4. Emergency UNIX and Linux Support

Appending the contents of two files in computational manner

Hi, I have two files say file 1 file 2 File1 1 2 4 5 File 2 asdf adf How to get the ouput something like asdf1 adf1 asdf2 adf2 asdf4 adf4 asdf5 (5 Replies)
Discussion started by: ecearund
5 Replies

5. AIX

How to use topas to display its Memory section alone

Hi, I'm planning to write a script to monitor the memory utilization and so decided to use topas. i'm not familiar with this command Could anyone help me with an idea on how to display the Memory section alone in the topas... :) It will be very helpful if you could specify the command... (2 Replies)
Discussion started by: kaushik_87
2 Replies

6. Shell Programming and Scripting

Capturing computational/non computational memory from topas

Hi Friends, How to capture the value of %Comp and %Noncomp values from AIX using topas command. I tried lot, but i cannot capture the value. (4 Replies)
Discussion started by: Nowshath
4 Replies

7. Shell Programming and Scripting

Shell script for %computational memory & % non computational memory

Dear, How to calculate %computational memory and %non computational memory from AIX server. What command used to find out %computational memory and % non computational memory except topas. Regards Nowshath (1 Reply)
Discussion started by: Nowshath
1 Replies
crashutil(1M)															     crashutil(1M)

NAME
crashutil - manipulate crash dump data SYNOPSIS
version] source [destination] DESCRIPTION
copies and preserves crash dump data, and performs format conversions on it. Common uses of include: o Copying portions of a dump that still reside on a raw dump device into a crash dump directory. o Converting between different formats of crash dumps. o Copying crash dumps from one directory, or medium, to another. will write to its destination the crash dump it reads from its source. The crash dump format used to write the destination is specified with if is not specified, the destination will have the same format as the source. If no destination is specified, source is used; the format conversion will be done in place in the source, without copying. When completes successfully, the entire contents of the crash dump will exist at destination; any portions that had still been on raw dump devices will have been copied to destination. There are three known dump formats: (Version 0) This format, used up through HP-UX 10.01, consists of a single file containing the physical memory image, with a 1-to-1 cor- respondence between file offset and memory address. Normally there is an associated file containing the kernel image. sources or destinations of this type must be specified as two pathnames to plain files, separated by whitespace; the first is the core image file and the second is the kernel image file. (Version 1) This format, used in HP-UX 10.10, 10.20, and 10.30, consists of a directory containing an file, the kernel file, and numerous files, which contain portions of the physical memory image. sources or destinations of this type should be specified as the pathname to a core directory. (Version 2) This format, used in HP-UX 11.00 and later, consists of a directory containing an file, the kernel and all dynamically loaded kernel module files, and numerous files, each of which contain portions of the physical memory image and metadata describing which memory pages were dumped and which were not. sources or destinations of this type should be specified as the pathname to a crash directory. (Version 3) This format is used in HP-UX Release 11i Version 1.0 and later. It is very similar in structure to the format in that it consists of a directory containing an file, the kernel and all dynamically loaded kernel module files, and numerous files, each of which contain portions of the physical memory image and metadata describing which memory pages were dumped and which were not. In addition to the primary file, there are auxiliary index files, that contain metadata describing the image files containing the memory pages. This format will be used when the dump is compressed. See crashconf(1M). Other formats, for example tape archival formats, may be added in the future. When the source and destination are different types of files -- for example, when source is a directory and destination is a pair of plain files -- both must be specified. Options (Quiet) Disables the printing of progress messages. Warning and error messages are still printed. Specifies the version of the destination format. Allowed values are 0, 1, 2 or 3. Also allowed is the keyword which specifies that the destination format should be the same as the current source format. is the default if is not specified. If the destination format is then the source format should also be Conversion to from older formats is not supported. RETURN VALUE
Upon exit, returns the following values: 0 The operation was successful. 1 The operation failed, and an appropriate error message was printed. EXAMPLES
An HP-UX 11.00 crash dump was saved by savecrash(1M) to The flag was specified to savecrash, specifying that only those portions of the dump which were endangered by swap activity should be saved; the rest are still resident in the raw dump devices. To save the remainder of the dump into the crash dump directory, use: If preferred, the completed crash dump directory could be in a different location -- perhaps on another machine via NFS: To debug this crash dump using tools which do not understand the most current crash dump format, convert it to the older core directory format: or the even older "core file and kernel" format: AUTHOR
was developed by HP. SEE ALSO
savecrash(1M), crashconf(1M). crashutil(1M)
All times are GMT -4. The time now is 10:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy