<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SHMMAX = Available Memory in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/shmmax-available-memory/m-p/3787485#M264322</link>
    <description>Let me say that this is a very dumb way to set SHMMAX. What should be done is to ask the DBA's what their largest anticipated SGA will need and set SHMMAX a bit above that. SHMMAX has almost nothing to do with the amount of physical memory in a system because HP-UX is a virtual memory based system; however, allowing a single process to grab all the available memory is normally considered a bad thing. Moreover, SHMMAX is a per-process limit rather than a system-wide limit so even with values much smaller than total memory size, it is possible to drive your box to its knees because of excessive swapping.&lt;BR /&gt;&lt;BR /&gt;Setting SHMMAX to a very large value does no harm in itself but it does allow the potential (intended or otherwise) for abuse there this should be a planned limit based upon maximum anticipated needs rather than&lt;BR /&gt;tying it to some value directly related to the total amount of physical memory. &lt;BR /&gt;</description>
    <pubDate>Fri, 12 May 2006 15:27:59 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2006-05-12T15:27:59Z</dc:date>
    <item>
      <title>SHMMAX = Available Memory</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/shmmax-available-memory/m-p/3787481#M264318</link>
      <description>In the setup for Oracle 10G on HP-UX 11.23, it specifies that SHMMAX should be set to Available Memory.&lt;BR /&gt;&lt;BR /&gt;How does one determine available memory?</description>
      <pubDate>Fri, 12 May 2006 12:57:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/shmmax-available-memory/m-p/3787481#M264318</guid>
      <dc:creator>Alan Meyer_4</dc:creator>
      <dc:date>2006-05-12T12:57:19Z</dc:date>
    </item>
    <item>
      <title>Re: SHMMAX = Available Memory</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/shmmax-available-memory/m-p/3787482#M264319</link>
      <description>pstat_getstatic() or Glance would be the most reliable way -- but since this is a fence line setting anyway, just set it to the amount of RAM on the box (it doesn't matter much if you don't account for the memory used by the kernel, etc.)</description>
      <pubDate>Fri, 12 May 2006 13:00:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/shmmax-available-memory/m-p/3787482#M264319</guid>
      <dc:creator>Don Morris_1</dc:creator>
      <dc:date>2006-05-12T13:00:44Z</dc:date>
    </item>
    <item>
      <title>Re: SHMMAX = Available Memory</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/shmmax-available-memory/m-p/3787483#M264320</link>
      <description>Use vmstat.&lt;BR /&gt;The "free" column is your free memory.</description>
      <pubDate>Fri, 12 May 2006 13:01:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/shmmax-available-memory/m-p/3787483#M264320</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2006-05-12T13:01:10Z</dc:date>
    </item>
    <item>
      <title>Re: SHMMAX = Available Memory</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/shmmax-available-memory/m-p/3787484#M264321</link>
      <description>Thanks for all your help.</description>
      <pubDate>Fri, 12 May 2006 13:33:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/shmmax-available-memory/m-p/3787484#M264321</guid>
      <dc:creator>Alan Meyer_4</dc:creator>
      <dc:date>2006-05-12T13:33:42Z</dc:date>
    </item>
    <item>
      <title>Re: SHMMAX = Available Memory</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/shmmax-available-memory/m-p/3787485#M264322</link>
      <description>Let me say that this is a very dumb way to set SHMMAX. What should be done is to ask the DBA's what their largest anticipated SGA will need and set SHMMAX a bit above that. SHMMAX has almost nothing to do with the amount of physical memory in a system because HP-UX is a virtual memory based system; however, allowing a single process to grab all the available memory is normally considered a bad thing. Moreover, SHMMAX is a per-process limit rather than a system-wide limit so even with values much smaller than total memory size, it is possible to drive your box to its knees because of excessive swapping.&lt;BR /&gt;&lt;BR /&gt;Setting SHMMAX to a very large value does no harm in itself but it does allow the potential (intended or otherwise) for abuse there this should be a planned limit based upon maximum anticipated needs rather than&lt;BR /&gt;tying it to some value directly related to the total amount of physical memory. &lt;BR /&gt;</description>
      <pubDate>Fri, 12 May 2006 15:27:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/shmmax-available-memory/m-p/3787485#M264322</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-05-12T15:27:59Z</dc:date>
    </item>
  </channel>
</rss>

