<?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: Problem with SAP not releasing shared memory segments in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-sap-not-releasing-shared-memory-segments/m-p/3999213#M296959</link>
    <description>As Clay mentioned, your shutdown procedure is defective. You and your DBA must examine all parts of the SAP and database shutdown procedure and determine where the missing or incorrect step is located. NOTE: any step with a kill -9 is very likely wrong.</description>
    <pubDate>Mon, 14 May 2007 10:30:21 GMT</pubDate>
    <dc:creator>Bill Hassell</dc:creator>
    <dc:date>2007-05-14T10:30:21Z</dc:date>
    <item>
      <title>Problem with SAP not releasing shared memory segments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-sap-not-releasing-shared-memory-segments/m-p/3999209#M296955</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;I wonder if anyone has seen this before. We have had the same problem on a number of SAP systems recently. We have made no changes on the OS and I am told (mmm!!!) no changes have been made on the application. Basically when SAP is shutdown it does not release the shared memory segments on the system and they appear in a De-activated state! We therefore cannot release them with an ipcrm command. This means we have to re-boot the server in order to be able to get SAP to start as it can't allocate sufficient shared memory. Has anybody seen symptoms like this before?&lt;BR /&gt;&lt;BR /&gt;Cheers</description>
      <pubDate>Mon, 14 May 2007 08:46:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-sap-not-releasing-shared-memory-segments/m-p/3999209#M296955</guid>
      <dc:creator>Adam Noble</dc:creator>
      <dc:date>2007-05-14T08:46:23Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with SAP not releasing shared memory segments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-sap-not-releasing-shared-memory-segments/m-p/3999210#M296956</link>
      <description>Sounds like there would be a process still attached after sap shutdown.&lt;BR /&gt;&lt;BR /&gt;When you issue ipcs -m after the shutdown,&lt;BR /&gt; - what does the NATTCH  column indicate?&lt;BR /&gt; - what does ps -ef | grep sap show?&lt;BR /&gt;&lt;BR /&gt;fwiw,&lt;BR /&gt;Hein.&lt;BR /&gt;</description>
      <pubDate>Mon, 14 May 2007 08:51:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-sap-not-releasing-shared-memory-segments/m-p/3999210#M296956</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2007-05-14T08:51:52Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with SAP not releasing shared memory segments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-sap-not-releasing-shared-memory-segments/m-p/3999211#M296957</link>
      <description>The NATTCH column shows 1 for all de-activated processes. I can't confirm as we have re-booted but believe its possible that processes were still on the system but in a zombie state. The problem is the processes can bot be killed and therefore the memory can't be released.</description>
      <pubDate>Mon, 14 May 2007 09:11:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-sap-not-releasing-shared-memory-segments/m-p/3999211#M296957</guid>
      <dc:creator>Adam Noble</dc:creator>
      <dc:date>2007-05-14T09:11:18Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with SAP not releasing shared memory segments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-sap-not-releasing-shared-memory-segments/m-p/3999212#M296958</link>
      <description>If you do a man shmctl (the system call that underlies ipcrm -m) and read the section that pertains to IPC_RMID, you will find that the behavior is analogous to that of unlink()ing a file. ie, the file is not actually removed until all the processes which have the file open eith close() the file or terminate. Similarly, shared memory segements aren't actually removed until all processes which have them attached either detach them or terminate. The solution to your problem is identical to that of your earlier posting. Find what is causing your processes not to terminate properly and you will solve your shared memory problems as a side effect.</description>
      <pubDate>Mon, 14 May 2007 09:20:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-sap-not-releasing-shared-memory-segments/m-p/3999212#M296958</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2007-05-14T09:20:38Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with SAP not releasing shared memory segments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-sap-not-releasing-shared-memory-segments/m-p/3999213#M296959</link>
      <description>As Clay mentioned, your shutdown procedure is defective. You and your DBA must examine all parts of the SAP and database shutdown procedure and determine where the missing or incorrect step is located. NOTE: any step with a kill -9 is very likely wrong.</description>
      <pubDate>Mon, 14 May 2007 10:30:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-sap-not-releasing-shared-memory-segments/m-p/3999213#M296959</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2007-05-14T10:30:21Z</dc:date>
    </item>
  </channel>
</rss>

