<?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: Progress database program in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/progress-database-program/m-p/2933129#M818802</link>
    <description>What does LOGTOOL say?&lt;BR /&gt;&lt;BR /&gt;STM &amp;gt; TOOLS &amp;gt; UTILITY &amp;gt; RUN &amp;gt; LOGTOOL &amp;gt; FILE &amp;gt; VIEW &amp;gt; RAW SUMMARY. &lt;BR /&gt;&lt;BR /&gt;Note the first and last dates of transactions and calculate the difference. If the difference is short, like 4 hours, then this is important to note. Now read down the report of hardware addresses and observe the integer numbers in parenthesis. Anything over 150 in this 4 hour period should be called into HP for replacement.&lt;BR /&gt;&lt;BR /&gt;sar -v 5 5&lt;BR /&gt;sar -d 5 5&lt;BR /&gt;sar -u 5 5&lt;BR /&gt;vmstat 5 5&lt;BR /&gt;&lt;BR /&gt;Please catenate and attach.</description>
    <pubDate>Fri, 21 Mar 2003 17:42:27 GMT</pubDate>
    <dc:creator>Michael Steele_2</dc:creator>
    <dc:date>2003-03-21T17:42:27Z</dc:date>
    <item>
      <title>Progress database program</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/progress-database-program/m-p/2933128#M818801</link>
      <description>Installed Progress 8.3.B database in striping logical volume in L-class server(HP-UX 11.0). After 3 weeks, database crash. Display I/O error from console. But, used "cstm" tool to check server hardware, no fail. Finally, delete striping disk group and restore database. No error occur again until now. Any body had this kind of experience? Please provide tips to identify this problem&lt;BR /&gt;&lt;BR /&gt;Ken</description>
      <pubDate>Fri, 21 Mar 2003 17:39:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/progress-database-program/m-p/2933128#M818801</guid>
      <dc:creator>kenlo</dc:creator>
      <dc:date>2003-03-21T17:39:23Z</dc:date>
    </item>
    <item>
      <title>Re: Progress database program</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/progress-database-program/m-p/2933129#M818802</link>
      <description>What does LOGTOOL say?&lt;BR /&gt;&lt;BR /&gt;STM &amp;gt; TOOLS &amp;gt; UTILITY &amp;gt; RUN &amp;gt; LOGTOOL &amp;gt; FILE &amp;gt; VIEW &amp;gt; RAW SUMMARY. &lt;BR /&gt;&lt;BR /&gt;Note the first and last dates of transactions and calculate the difference. If the difference is short, like 4 hours, then this is important to note. Now read down the report of hardware addresses and observe the integer numbers in parenthesis. Anything over 150 in this 4 hour period should be called into HP for replacement.&lt;BR /&gt;&lt;BR /&gt;sar -v 5 5&lt;BR /&gt;sar -d 5 5&lt;BR /&gt;sar -u 5 5&lt;BR /&gt;vmstat 5 5&lt;BR /&gt;&lt;BR /&gt;Please catenate and attach.</description>
      <pubDate>Fri, 21 Mar 2003 17:42:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/progress-database-program/m-p/2933129#M818802</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2003-03-21T17:42:27Z</dc:date>
    </item>
    <item>
      <title>Re: Progress database program</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/progress-database-program/m-p/2933130#M818803</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;what kind of I/O error, I'd like to see the entire error message.&lt;BR /&gt;Also, have you checked the &lt;DATABASE&gt;.lg file to see any Progress error message?&lt;BR /&gt;&lt;/DATABASE&gt;</description>
      <pubDate>Mon, 24 Mar 2003 15:23:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/progress-database-program/m-p/2933130#M818803</guid>
      <dc:creator>Julio Yamawaki</dc:creator>
      <dc:date>2003-03-24T15:23:52Z</dc:date>
    </item>
  </channel>
</rss>

