<?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: Mem Checking Help in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/mem-checking-help/m-p/2565102#M29818</link>
    <description>It is very unlikely that a true RAM problem such as a parity error) would go unnoticed...there will be lots of logged errors. It's unfortunate that the actual reason for the Oracle problem does not return a Unix error code as this would greatly simplify the fix.&lt;BR /&gt;&lt;BR /&gt;The sar -v output you are looking at has only 2 useful values, proc-sz and file-sz.  The inode-sz entry is a measure of the cache usage and should normally be 100% after a few hours following a reboot.&lt;BR /&gt;&lt;BR /&gt;The most common parameters that need changing for database servers are:&lt;BR /&gt;&lt;BR /&gt;nproc&lt;BR /&gt;nfile&lt;BR /&gt;maxdsiz&lt;BR /&gt;maxuprc&lt;BR /&gt;&lt;BR /&gt;There are application-specific values such as semaphores but these are usually very explicit from the database manufacturer.  Start by doubling nproc, nfile and maxdsiz.  maxuprc won't need to be changed unless you have dozens of users logging in as the same username.</description>
    <pubDate>Wed, 15 Aug 2001 02:11:21 GMT</pubDate>
    <dc:creator>Bill Hassell</dc:creator>
    <dc:date>2001-08-15T02:11:21Z</dc:date>
    <item>
      <title>Mem Checking Help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mem-checking-help/m-p/2565095#M29811</link>
      <description>I would appreciate it very much if someone can give me some confidence about how to check memory on 10.20 of K box.&lt;BR /&gt;&lt;BR /&gt;I have problem on database crash with possible cause of memory (physical) or user process overflow (according to Oracle).   While none is identified, i.e. no message indicates OS problem and memory bad, as well as database processes bad, I would see if hp guru have any thought.&lt;BR /&gt;&lt;BR /&gt;dmesg, ipcs, glance, swapinfo are what I have used.&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;Steven</description>
      <pubDate>Tue, 14 Aug 2001 11:46:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mem-checking-help/m-p/2565095#M29811</guid>
      <dc:creator>Steven Chen_1</dc:creator>
      <dc:date>2001-08-14T11:46:54Z</dc:date>
    </item>
    <item>
      <title>Re: Mem Checking Help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mem-checking-help/m-p/2565096#M29812</link>
      <description>Hi Steven:&lt;BR /&gt;&lt;BR /&gt;From a software (O/S) perspective, you are using the right tools to assess memory utilization.&lt;BR /&gt;&lt;BR /&gt;IF you want to satisfy yourself that your physical memory is good you can view its configuration and error levels with the Support Tools Manager (STM): &lt;BR /&gt;&lt;BR /&gt;# echo "selclass qualifier memory;info;wait;infolog"|cstm &amp;gt; /tmp/meminfo&lt;BR /&gt;&lt;BR /&gt;Remember that single-bit errors are automatically corrected, and should not impact application software.  A growing number of single bit errors is a warning to get a memory sim replaced, however.&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Tue, 14 Aug 2001 11:58:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mem-checking-help/m-p/2565096#M29812</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2001-08-14T11:58:10Z</dc:date>
    </item>
    <item>
      <title>Re: Mem Checking Help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mem-checking-help/m-p/2565097#M29813</link>
      <description>Hi,&lt;BR /&gt;SAM--&amp;gt;performance monitor--&amp;gt;system properties--&amp;gt;meory gives the physical memory and swap info&lt;BR /&gt;&lt;BR /&gt;If the database showing process over flow check the nproc in kernel parameter, orcale recommends 4096.</description>
      <pubDate>Tue, 14 Aug 2001 11:58:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mem-checking-help/m-p/2565097#M29813</guid>
      <dc:creator>Ravi_8</dc:creator>
      <dc:date>2001-08-14T11:58:56Z</dc:date>
    </item>
    <item>
      <title>Re: Mem Checking Help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mem-checking-help/m-p/2565098#M29814</link>
      <description>Hi Steven,&lt;BR /&gt;&lt;BR /&gt;To determine the actual physical memory available on the system.&lt;BR /&gt;&lt;BR /&gt;1. dmesg | grep Physical&lt;BR /&gt;(if it hasn't been too long since the machine reboot).&lt;BR /&gt;&lt;BR /&gt;2. /usr/sam/lbin/getmem&lt;BR /&gt;(This command has to be run by root, gives the output in MB)&lt;BR /&gt;&lt;BR /&gt;If you are looking for the actual location of the symm and their sizes, one of the easiest ways without reboot the system is to use cstm/mstm/xsm.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;-HTH&lt;BR /&gt;I am RU</description>
      <pubDate>Tue, 14 Aug 2001 12:49:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mem-checking-help/m-p/2565098#M29814</guid>
      <dc:creator>linuxfan</dc:creator>
      <dc:date>2001-08-14T12:49:32Z</dc:date>
    </item>
    <item>
      <title>Re: Mem Checking Help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mem-checking-help/m-p/2565099#M29815</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;You can use this C-program which shows you the available memory of you K server.&lt;BR /&gt;&lt;BR /&gt;PJA</description>
      <pubDate>Tue, 14 Aug 2001 12:58:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mem-checking-help/m-p/2565099#M29815</guid>
      <dc:creator>JACQUET</dc:creator>
      <dc:date>2001-08-14T12:58:25Z</dc:date>
    </item>
    <item>
      <title>Re: Mem Checking Help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mem-checking-help/m-p/2565100#M29816</link>
      <description>Thank you all for the great help.   I am unable to assign points yet.&lt;BR /&gt;&lt;BR /&gt;For deeper inspection, can you help finding any problem on ninode in kernel parameters?   The sar -v result is:&lt;BR /&gt;&lt;BR /&gt;-----------------------&lt;BR /&gt;&lt;BR /&gt;#sar -v 5 5&lt;BR /&gt;&lt;BR /&gt;HP-UX B.10.20 C 9000/879    08/14/01&lt;BR /&gt;&lt;BR /&gt;10:08:50 text-sz  ov  proc-sz  ov  inod-sz  ov  file-sz  ov &lt;BR /&gt;10:08:55   N/A   N/A 197/3620  0  3894/4418  0  814/6779  0&lt;BR /&gt;10:09:00   N/A   N/A 197/3620  0  3893/4418  0  814/6779  0&lt;BR /&gt;10:09:05   N/A   N/A 197/3620  0  3895/4418  0  814/6779  0&lt;BR /&gt;10:09:10   N/A   N/A 197/3620  0  3888/4418  0  814/6779  0&lt;BR /&gt;10:09:15   N/A   N/A 198/3620  0  3894/4418  0  817/6779  0&lt;BR /&gt;&lt;BR /&gt;---------------------&lt;BR /&gt;&lt;BR /&gt;I see inod-sz is close.   Do I have to adjust it from kernel?&lt;BR /&gt;&lt;BR /&gt;Thanks a lot.&lt;BR /&gt;&lt;BR /&gt;Steven</description>
      <pubDate>Tue, 14 Aug 2001 13:23:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mem-checking-help/m-p/2565100#M29816</guid>
      <dc:creator>Steven Chen_1</dc:creator>
      <dc:date>2001-08-14T13:23:28Z</dc:date>
    </item>
    <item>
      <title>Re: Mem Checking Help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mem-checking-help/m-p/2565101#M29817</link>
      <description>Hi Steven,&lt;BR /&gt;&lt;BR /&gt;You can change the kernel parameters is multiple ways. One of the ways is use SAM to change the kernel parameter. Mind you this change will require a reboot of the system.&lt;BR /&gt;&lt;BR /&gt;To find out more information about the various configurable kernel parameters you can look at&lt;BR /&gt;&lt;A href="http://docs.hp.com/hpux/onlinedocs/os/KCparams.OverviewAll.html" target="_blank"&gt;http://docs.hp.com/hpux/onlinedocs/os/KCparams.OverviewAll.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;-HTH&lt;BR /&gt;I am RU</description>
      <pubDate>Tue, 14 Aug 2001 16:20:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mem-checking-help/m-p/2565101#M29817</guid>
      <dc:creator>linuxfan</dc:creator>
      <dc:date>2001-08-14T16:20:20Z</dc:date>
    </item>
    <item>
      <title>Re: Mem Checking Help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mem-checking-help/m-p/2565102#M29818</link>
      <description>It is very unlikely that a true RAM problem such as a parity error) would go unnoticed...there will be lots of logged errors. It's unfortunate that the actual reason for the Oracle problem does not return a Unix error code as this would greatly simplify the fix.&lt;BR /&gt;&lt;BR /&gt;The sar -v output you are looking at has only 2 useful values, proc-sz and file-sz.  The inode-sz entry is a measure of the cache usage and should normally be 100% after a few hours following a reboot.&lt;BR /&gt;&lt;BR /&gt;The most common parameters that need changing for database servers are:&lt;BR /&gt;&lt;BR /&gt;nproc&lt;BR /&gt;nfile&lt;BR /&gt;maxdsiz&lt;BR /&gt;maxuprc&lt;BR /&gt;&lt;BR /&gt;There are application-specific values such as semaphores but these are usually very explicit from the database manufacturer.  Start by doubling nproc, nfile and maxdsiz.  maxuprc won't need to be changed unless you have dozens of users logging in as the same username.</description>
      <pubDate>Wed, 15 Aug 2001 02:11:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mem-checking-help/m-p/2565102#M29818</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2001-08-15T02:11:21Z</dc:date>
    </item>
    <item>
      <title>Re: Mem Checking Help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mem-checking-help/m-p/2565103#M29819</link>
      <description>Hi&lt;BR /&gt;  When running oracle it helps to check the values of&lt;BR /&gt;dynamic cache&lt;BR /&gt;dbc_max_pct&lt;BR /&gt;&lt;BR /&gt;Shared memory related values&lt;BR /&gt;shmmax&lt;BR /&gt;shmmni&lt;BR /&gt;shmseg&lt;BR /&gt;&lt;BR /&gt;  also check the value of semaphores&lt;BR /&gt;SEMMNS&lt;BR /&gt;SEMMNI&lt;BR /&gt;&lt;BR /&gt;...BPK...&lt;BR /&gt;</description>
      <pubDate>Wed, 15 Aug 2001 08:02:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mem-checking-help/m-p/2565103#M29819</guid>
      <dc:creator>Praveen Bezawada</dc:creator>
      <dc:date>2001-08-15T08:02:51Z</dc:date>
    </item>
  </channel>
</rss>

