RP/TMA 8.1 (OSITP) - Can''t detach shared memory segment from the process
(Doc ID 777350.1)
Last updated on SEPTEMBER 06, 2022
Applies to:Oracle Tuxedo - Version 8.1 and later
Information in this document applies to any platform.
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: /path/to/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-- <unixAdminUser> <unixAdminGroup> m 1805 0 --rw------- <unixUser> <unixGrp> m 1806 0 --rw------- <unixUser> <unixGrp> m 1807 0 --rw------- <unixUser> <unixGrp> Semaphores: /path/to/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 eventually. This problem appears to happen only on the Solaris system. CONFIGURATION: TMA OSITP 8.1 Solaris
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document