- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Ideas for checking shared memory fragmentation
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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-24-2002 08:48 AM
01-24-2002 08:48 AM
My platform: N-class (UX-11.00) 5G RAM, 9G Dev swap, active in kernel: shmem=1, shmmax=212748365, shmseg=64
We are running oracle 11i and are trying to have three concurrent databases up and am experiencing problems occasionally with shmem allocation. i.e. on system startup all three will come up fine, no problems. Later if we bring one database down and up again, or a different one up, we get shmem cannot allocate space issues. So I'm trying to go through the routing of checking where we stand with shmem to see what our best course of action is.
I understand (i think) about the 1.75g limit on shmem, unless I am using shmem windows & *_magic implementations. Not exactly sure if I am using full *_magic implementation or not, since when I run the shminfo script (a great utility I got from HP-support, along with other shmem diag tools - check it out see attached)I see info for [shared space from window id 0 (global) for quadrant 2&3, and shared space from window id 1 (q3private)]. Not sure if all required patches are installed for support for shmem windows or *_magic, but do have the following installed: 11.00 PHSS_19866 (chatr +q3p enable), 11.00 PHKL_20995 (q3 private fix), 11.00 PHKL_22493
Anyway, your thoughts/observations on diagnosing shmem fragmentation & related issues. Also, has anybody run 'adb' against 11.00 to check for fragmentation and if so, how and what to look for?
I will try to attatch all 4 files about shmem util, not sure if it will work??
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2002 08:50 AM
01-24-2002 08:50 AM
Re: Ideas for checking shared memory fragmentation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2002 08:51 AM
01-24-2002 08:51 AM
Re: Ideas for checking shared memory fragmentation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2002 08:52 AM
01-24-2002 08:52 AM
Re: Ideas for checking shared memory fragmentation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2002 08:52 AM
01-24-2002 08:52 AM
Re: Ideas for checking shared memory fragmentation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2002 08:59 AM
01-24-2002 08:59 AM
Re: Ideas for checking shared memory fragmentation
I don't think 1.75 is a limitation for memory segements running 64 bit applications. Are your databases 64 bit or 32 bit. If you are 64 bit you don't have the 1.75 limitation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2002 09:03 AM
01-24-2002 09:03 AM
Re: Ideas for checking shared memory fragmentation
I have mine set to
shmmax 18000000000
shemni 256
shmseg 200
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2002 09:05 AM
01-24-2002 09:05 AM
Re: Ideas for checking shared memory fragmentation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2002 09:26 AM
01-24-2002 09:26 AM
Re: Ideas for checking shared memory fragmentation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2002 12:58 PM
01-24-2002 12:58 PM
Re: Ideas for checking shared memory fragmentation
How hard would it be to upgrade Oracle to 64bit? This is a better fix.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2002 08:14 AM
01-25-2002 08:14 AM
Re: Ideas for checking shared memory fragmentation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2002 08:20 AM
01-25-2002 08:20 AM
Re: Ideas for checking shared memory fragmentation
Try this link,
http://us-support3.external.hp.com/cki/bin/doc.pl/sid=69e4639c01505c4896/screen=ckiDisplayDocument?docId=200000045618004
Hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2002 08:31 AM
01-25-2002 08:31 AM
SolutionIf it is a test system consider lowering the SGA. If it is lightly used.
When we have ran two SAP systems on the same server and one was 32bit we had to lower all the shared memory parms for SAP as low as possible, along with the Oracle SGA. ( This will only help if it is lightly used. )
One option of course is to add more memory. The reason you can't start apps after shutting down is because one or all three of the apps have used all the shared memory available and had to swapout information and started to use physical memory at random. When this happens it takes pieces of each quadrant so when you start backup it can not get any contigous memory address in any quadrant to fulfil your shared memory request. So with 5 gb of memory divided by 4 you only start with 1.25 GB. You are not even at the 1.75 limit. Also keep in mind one of the quadrants takes some for the OS, so only 3 or the 4 gets 1.25.
My next question may be dump but I will ask it anyway. Is it possible to run your Database at 64bit and run your Oracle App at 32bit?
If I understand correctly Oracle 11i is your software app. What is the version of your DB engine? I think 9i is the highest DB release.
If you can run the database at 64bit it might help starting Oracle to allocated a big enough SGA. Your apps will of course continue to have the same problem. I just don't know it is possible in your environment.