- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Shared memory table nearly full
Operating System - HP-UX
1748158
Members
4242
Online
108758
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2005 05:59 AM
тАО01-10-2005 05:59 AM
Shared memory table nearly full
Hey all, in glance I am getting a 'Shared Memory Table is nearly full' message. Then I get a 'end of shared memory table full condition'. This started about four weeks ago and I am lost on what to look for. The pattern seems to start around 12:30pm EST and last for a couple hours. I am runn a N4000 with 8.5 GB of memory and HP 11.11. I am not expert by any means, so could someone please HELP.
Matt
Matt
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2005 06:05 AM
тАО01-10-2005 06:05 AM
Re: Shared memory table nearly full
Matt,
You should think about increasing the kernel parameter "shmmni".
Pete
Pete
You should think about increasing the kernel parameter "shmmni".
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2005 06:44 AM
тАО01-10-2005 06:44 AM
Re: Shared memory table nearly full
The problem is with your 32bit applications. There is only one map for shared memory for all programs and it becomes fragmented when you stop and start various programs that use shared memory. And shared memory segments that were in use by programs that were killed with kill -9 will occupy this space until a reboot (kill -9 should always be avoided if at all possible for database and other complex programs). You can start by looking at the shared mmemory table assignments:
ipcs -bmop
Now you can remove segments that are no longer in use but this requires detailed knowledge of the programs that are currently running. The NATTCH field shows a process count that is using this segment. Anything > 0 means that it is in use. But NATTCH=0 is not always a sign that the segment is no longer used. It's possible that some processes may be scheduled in the near future that will indeed use this segment. You can also check the CPID, the process ID of the creator of this segment, and LPID, the last process ID that either attached or detached from the segment. The command ipcrm can remove a segment to free some memory, but if the segment is still in use, the affected programs will crash.
The safest way to handle this situation is to reboot, then have your programmers or DBAs look at ways to properly shutdown the programs while running and have the shared memory segments removed. There are two other solutions: memory windows and changing the 32bit programs to 64bit programs. Memory windows is probably the simplest solution. This gives each group of programs that need shared memory their own private memory map so that fragmentation is virtually eliminated.
The 32bit shared memory map is used by many different programs such as fbackup and also includes very small pieces of memory used by daemons and other system programs. If you'd like to see the complete usage (in memory order), get a copy of shminfo from: ftp://contrib:9unsupp8@hprc.external.hp.com/sysadmin/programs/shminfo/
Bill Hassell, sysadmin
ipcs -bmop
Now you can remove segments that are no longer in use but this requires detailed knowledge of the programs that are currently running. The NATTCH field shows a process count that is using this segment. Anything > 0 means that it is in use. But NATTCH=0 is not always a sign that the segment is no longer used. It's possible that some processes may be scheduled in the near future that will indeed use this segment. You can also check the CPID, the process ID of the creator of this segment, and LPID, the last process ID that either attached or detached from the segment. The command ipcrm can remove a segment to free some memory, but if the segment is still in use, the affected programs will crash.
The safest way to handle this situation is to reboot, then have your programmers or DBAs look at ways to properly shutdown the programs while running and have the shared memory segments removed. There are two other solutions: memory windows and changing the 32bit programs to 64bit programs. Memory windows is probably the simplest solution. This gives each group of programs that need shared memory their own private memory map so that fragmentation is virtually eliminated.
The 32bit shared memory map is used by many different programs such as fbackup and also includes very small pieces of memory used by daemons and other system programs. If you'd like to see the complete usage (in memory order), get a copy of shminfo from: ftp://contrib:9unsupp8@hprc.external.hp.com/sysadmin/programs/shminfo/
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2005 07:28 AM
тАО01-10-2005 07:28 AM
Re: Shared memory table nearly full
Thanks for the response guys. I reboot the system Friday and it started again today. The only thing I can think of is that we have grown some .Net applications that call an ODBC pacakage called UniObjects that inturn uses a UNIX login. It is a many to few situation of .Net user to UNIX accounts. I am wondering if the same UNIX account is called many times will this fill up the shared memory? At this point I think I need to increase the shared memory as we have 8.5 of physical memory and based on glance use 65% of the physical and 49% of the swap on an average. What do you guys think? What all goes into increasing shared memory? reboot? etc?
Matt
Matt
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP