RP/TMA 8.1 (OSITP) - Can''t detach shared memory segment from the process

(Doc ID 777350.1)

Last updated on JANUARY 19, 2018

Applies to:

Oracle Tuxedo / TMA OSI TP / 8,1
Information in this document applies to any platform


ERROR: Can't detach shared memory segment from the process.

It happens even if you do a tmboot -y then a tmshutdown -y starting out with a clean system and running nothing but
startup and shutdown.

When the customer does ipcs, they get:
sun4:/var/opt/tuxde81/log > ipcs
IPC status from <running system> as of Wed Jun  7 12:52:04 EDT 2006
T         ID      KEY        MODE        OWNER    GROUP
Message Queues:
Shared Memory:
m          0   0x500005cc --rw-r--r--     root     root
m       1805   0          --rw-------    tux81   tuxgrp
m       1806   0          --rw-------    tux81   tuxgrp
m       1807   0          --rw-------    tux81   tuxgrp
sun4:/var/opt/tuxde81/log > 

It looks like each time when GWOSITP shuts down, and it leaves behind three shared memory segments that do not get
cleaned up.  

So, this looks like a problem that needs to be addressed, otherwise the user will run out of shared memory segments

This problem appears to happen only on the Solaris system.



Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms