Shared memory segment with 0 attaches

[Juan Canjura]

Hi,

I just run a sys_check on a 3-node Tru64 Cluster and found some messages similar to this one:

Operational: Shared memory segment with 0 attaches ( 5243056 ).
This is should be investigated. This may be normal, or may mean shared memory was not properly released.

I've been searching for some light on this but couldn't anything yet. What does this mean? (or better) is there any way to find out if that could be a performance issue?

Thanks in advance.

Juan

[Victor Semaska_3]

Juan,

I get those messages all the time when I run sys_check. Check with the ipcs command like this:

# ipcs -bom

Shared Memory:
T ID KEY MODE OWNER GROUP NATTCH SEGSZ
m 0 0x435dce60 --rw-rw-rw- root system 1 8024
m 1 0x615d045c --rw------- root daemon 0 57776

The NATTCH column is the no. attached. I get the error message because of the 2nd one. Don't know why it's there, I simply ignore them.

Vic


Vic

[Ivan Ferreira · Accepted solution]

Shared memory is used for process communications. Normally, databases make extensive use of shared memory.

When the database starts, or a process that uses shared memory start, it creates the shared memory segment. Normally, one or more process are attached to the shared memory segment to exchange information.

There could be the case, that a process creates a shared memory segment, but when it ends, does not closes the shared memory segment created. If is not used, then is consuming memory without needs.

You can view the CPID/LPID to identify the current and last process ID that used the shared memory segment. You can also identify the creator by looking at the CREATOR CGROUP fields.

[Juan Canjura]

Fair enough, thank you both.

Juan