<?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: Crash Analysis Help in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/crash-analysis-help/m-p/2564672#M919616</link>
    <description>Steven,&lt;BR /&gt;&lt;BR /&gt;Have you monitored swap utilization?&lt;BR /&gt;What does 'swapinfo -tam' show?&lt;BR /&gt;In any case, if you have enough disk for about 2Gb of swap device, I would suggest disabling pseudo-swap&lt;BR /&gt;(change the kernel parameter 'swapmem_on' to 0)&lt;BR /&gt;&lt;BR /&gt;Regards ...   Mladen</description>
    <pubDate>Mon, 13 Aug 2001 15:59:26 GMT</pubDate>
    <dc:creator>Mladen Despic</dc:creator>
    <dc:date>2001-08-13T15:59:26Z</dc:date>
    <item>
      <title>Crash Analysis Help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/crash-analysis-help/m-p/2564671#M919615</link>
      <description>Hi,&lt;BR /&gt; &lt;BR /&gt;I would like to have HP+Oracle guru to analyse the suddent Oracle crash last Friday.   Your any comments are very apprciated.&lt;BR /&gt;&lt;BR /&gt;Os is hpux 10.20, Oracle is V732.   Physical Mem is 1G, Physical: 1048564 Kbytes, lockable: 778008 Kbytes, available: 895064 Kbytes.    Oracle sga is 400M.&lt;BR /&gt;&lt;BR /&gt;The crash was regarded either a memory false or process overflow that exceed memory.   In any case, the reco process was not able to recover.   Db was dead then.   I had to recover all from the point of crash.&lt;BR /&gt;&lt;BR /&gt;It would be interested for all viewers to learn from this instance.   For your expertise, I would post the kernel configuration for your comment.&lt;BR /&gt;&lt;BR /&gt;Thanks a lot first,&lt;BR /&gt;&lt;BR /&gt;Steven&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 13 Aug 2001 12:32:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/crash-analysis-help/m-p/2564671#M919615</guid>
      <dc:creator>Steven Chen_1</dc:creator>
      <dc:date>2001-08-13T12:32:24Z</dc:date>
    </item>
    <item>
      <title>Re: Crash Analysis Help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/crash-analysis-help/m-p/2564672#M919616</link>
      <description>Steven,&lt;BR /&gt;&lt;BR /&gt;Have you monitored swap utilization?&lt;BR /&gt;What does 'swapinfo -tam' show?&lt;BR /&gt;In any case, if you have enough disk for about 2Gb of swap device, I would suggest disabling pseudo-swap&lt;BR /&gt;(change the kernel parameter 'swapmem_on' to 0)&lt;BR /&gt;&lt;BR /&gt;Regards ...   Mladen</description>
      <pubDate>Mon, 13 Aug 2001 15:59:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/crash-analysis-help/m-p/2564672#M919616</guid>
      <dc:creator>Mladen Despic</dc:creator>
      <dc:date>2001-08-13T15:59:26Z</dc:date>
    </item>
    <item>
      <title>Re: Crash Analysis Help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/crash-analysis-help/m-p/2564673#M919617</link>
      <description>You could disable dynamic buffer cache&lt;BR /&gt;by setting bufpages to a value different from 0, e.g. 10000 (40megs) to avoid possible allocation/deallocation of buffer pages.&lt;BR /&gt;&lt;BR /&gt;Verify you have the latest HPUX kernel patches&lt;BR /&gt;installed.&lt;BR /&gt;&lt;BR /&gt;Consider updating Oracle RDBMS to the latest&lt;BR /&gt;patch level, there are many issues related&lt;BR /&gt;to excessive memory allocation by snapshot&lt;BR /&gt;or shadow processes and processes not releasing&lt;BR /&gt;memory.</description>
      <pubDate>Thu, 16 Aug 2001 06:54:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/crash-analysis-help/m-p/2564673#M919617</guid>
      <dc:creator>Alessandro Bocchino</dc:creator>
      <dc:date>2001-08-16T06:54:13Z</dc:date>
    </item>
  </channel>
</rss>

