01-19-2015
I think you should look at shared memory as well. That uses paging as a backing store.
If you allocate a shared memory block for a database instance, it allocates swap as well as memory. So the amount of swap used by the db limits the virtual memory other process can acquire, or show as swap being used up by otherwise normal operations.
Since this is AIX I do not know the command analogous to ipcs found every where else.
You need to see what percent of memory is used as shared memory segments.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
I need explanations about physical disks and physical volumes. What is the difference between these 2 things?
In fact, i am trying to understand what the AIX lspv2command does.
Thank you in advance. (2 Replies)
Discussion started by: VeroL
2 Replies
2. UNIX for Dummies Questions & Answers
Hi All,
I have a pair of sun ultra 5_10 with SunOS 5.5.1.
Both are almost equally patched and set up with simillar applications.
host# uname -a
SunOS host 5.5.1 Generic_103640-24 sun4u sparc SUNW,Ultra-5_10
Even though both have
same amount of RAM ( 512 Mb ) ,
... (1 Reply)
Discussion started by: shibz
1 Replies
3. UNIX for Dummies Questions & Answers
I was in smit, checking on disc space, etc. and it appears that one of our physical volumes that is part of a large volume group, has no free physical partitions. The server is running AIX 5.1. What would be the advisable step to take in this instance? (9 Replies)
Discussion started by: markper
9 Replies
4. Linux
What is amount of free RAM i have now?
total used free shared buffers cached
Mem: 1010 963 46 0 215 256
-/+ buffers/cache: 491 518
Swap: 1983 0 1983
Above is the output of... (1 Reply)
Discussion started by: new2ss
1 Replies
5. Solaris
We have Sun OS running on spark :
SunOS ciniwnpr67 5.10 Generic_118833-24 sun4u sparc SUNW,Sun-Fire-V440
Having Physical RAM :
Sol10box # prtconf | grep Mem
Memory size: 8192 Megabytes
My Top Output is :
130 processes: 129 sleeping, 1 on cpu
CPU states: 98.8% idle, 0.2% user, 1.0%... (27 Replies)
Discussion started by: rajwinder
27 Replies
6. AIX
Hello All,
Can anybody please tell me what is the maximum limit of Physical IBM Power Machine which can be handled by single HMC at a single point of time?
Thanks,
Jenish (1 Reply)
Discussion started by: jenish_shah
1 Replies
7. Solaris
After a memory upgrade all network interfaces are misconfigued. How do i resolve this issue. Below are some out puts.thanks.
ifconfig: plumb: SIOCLIFADDIF: eg000g0:2: no such interface
# ifconfig eg1000g0:2 plumb
ifconfig: plumb: SIOCLIFADDIF: eg1000g0:2: no such interface
# ifconfig... (2 Replies)
Discussion started by: andersonedouard
2 Replies
8. Solaris
<A href="mailto:root@sssdpmds01$">
root@sssdpmds01$ prstat -a
PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP
13831 ogw 2613M 2108M cpu12 0 0 277:43:27 3.9% java/1201
4312 ogw 2641M 2092M sleep 59 0 562:45:51 2.1% java/1235
4469 ogw ... (2 Replies)
Discussion started by: jojo123
2 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies
1)Physical Volume
2)Volume Group
3)Logical Volume
4)Physical Partition
Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies
10. Solaris
Hi,
When I run the free command on solaris, I get the following:
"Memory: 60G phys mem, 69G free mem"
Q: how cna the free mem be higher then the physical mem?:confused:
Amit (3 Replies)
Discussion started by: amitlib
3 Replies
LEARN ABOUT NETBSD
shmget
SHMGET(2) BSD System Calls Manual SHMGET(2)
NAME
shmget -- get shared memory segment
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <sys/shm.h>
int
shmget(key_t key, size_t size, int shmflg);
DESCRIPTION
shmget() returns the shared memory identifier associated with the key key.
A shared memory segment is created if either key is equal to IPC_PRIVATE, or key does not have a shared memory segment identifier associated
with it, and the IPC_CREAT bit is set in shmflg. If both the IPC_CREAT bit and the IPC_EXCL bit are set in shmflg, and key has a shared mem-
ory segment identifier associated with it already, the operation will fail.
If a new shared memory segment is created, the data structure associated with it (the shmid_ds structure, see shmctl(2)) is initialized as
follows:
o shm_perm.cuid and shm_perm.uid are set to the effective uid of the calling process.
o shm_perm.gid and shm_perm.cgid are set to the effective gid of the calling process.
o shm_perm.mode is set to the lower 9 bits of shmflg.
o shm_lpid, shm_nattch, shm_atime, and shm_dtime are set to 0.
o shm_ctime is set to the current time.
o shm_segsz is set to the value of size.
RETURN VALUES
Upon successful completion a positive shared memory segment identifier is returned. Otherwise, -1 is returned and the global variable errno
is set to indicate the error.
ERRORS
[EACCES] A shared memory segment is already associated with key and the caller has no permission to access it.
[EEXIST] Both IPC_CREAT and IPC_EXCL are set in shmflg, and a shared memory segment is already associated with key.
[EINVAL] No shared memory segment is to be created, and a shared memory segment exists for key, but the size of the segment associ-
ated with it is less than size, which is non-zero.
A shared memory segment is to be created, and size is less than the system imposed minimum, or greater than the system
imposed maximum (refer to the kern.ipc values in sysctl(7)).
[ENOENT] IPC_CREAT is not set in shmflg and no shared memory segment associated with key was found.
[ENOMEM] There is not enough memory left to create a shared memory segment of the requested size.
[ENOSPC] A new shared memory identifier could not be created because the system limit for the number of shared memory identifiers
has been reached.
SEE ALSO
ipcrm(1), ipcs(1), mmap(2), shmat(2), shmctl(2), ftok(3), sysctl(7)
STANDARDS
The shmget system call conforms to X/Open System Interfaces and Headers Issue 5 (``XSH5'').
HISTORY
Shared memory segments appeared in the first release of AT&T System V UNIX.
BSD
October 27, 2008 BSD