<?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: SGeSAP problems with PHSS_38923 in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/sgesap-problems-with-phss-38923/m-p/5156781#M671518</link>
    <description>As previously said, problem gone away when reverting back to SGeSAP scripts delivered with initial release of SGeSAP. No time to investigate and understand ... :-( May be next time.</description>
    <pubDate>Mon, 02 Mar 2009 09:35:15 GMT</pubDate>
    <dc:creator>Eric SAUBIGNAC</dc:creator>
    <dc:date>2009-03-02T09:35:15Z</dc:date>
    <item>
      <title>SGeSAP problems with PHSS_38923</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sgesap-problems-with-phss-38923/m-p/5156778#M671515</link>
      <description>Bonsoir,&lt;BR /&gt;&lt;BR /&gt;Has someone tested latest scripts delivered with PHSS_38923 "SGeSAP B.04.51.00 Cumulative Patch" ?&lt;BR /&gt;&lt;BR /&gt;Halting package dbci is a disaster : rfc test and corresponding watchdog hanged, long and ineffective stop of igs, some processes still running, ipcs still present after package is stopped, ... :-((((( And I get those errors on the DBCI itself, not yet tested in a failover configuration [ and I guess I will no more loose time to do this test ].&lt;BR /&gt;&lt;BR /&gt;By chance, database is correctly stopped. Most important !&lt;BR /&gt;&lt;BR /&gt;My configuration is very basic : 1 package with a DBCI that can failover to an AS. And 2 other externals AS servers. HP-UX 11iv3 0809, SAP ECC6 / Oracle 10g. And every things worked very well before patching with PHSS_38923.&lt;BR /&gt;&lt;BR /&gt;What I did after patching was to update /etc/cmcluster/sap.functions /etc/cmcluster/P01/sap.config and /etc/cmcluster/P01/sapwas.cntl from updated repository /opt/cmcluster/sap. That's all. Did I miss something ? New parameters to configure ? Known bug ?&lt;BR /&gt;&lt;BR /&gt;I guess I will do a rollback, but I would like to understand before giving up :-(&lt;BR /&gt;&lt;BR /&gt;Eric</description>
      <pubDate>Thu, 12 Feb 2009 19:00:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sgesap-problems-with-phss-38923/m-p/5156778#M671515</guid>
      <dc:creator>Eric SAUBIGNAC</dc:creator>
      <dc:date>2009-02-12T19:00:43Z</dc:date>
    </item>
    <item>
      <title>Re: SGeSAP problems with PHSS_38923</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sgesap-problems-with-phss-38923/m-p/5156779#M671516</link>
      <description>It is hard to identify the problem w/o package logs. I really suggest you open a call with HP Support. &lt;BR /&gt;&lt;BR /&gt;When the watchdog does not finish this usually means that the process it is monitoring does not finish. I would not regard this as a problem of the SGeSAP in the first place: in the end SGeSAP often starts an SAP command and when this hangs this would often (but not always) be an SAP problem. Hard to judge with no logs though. &lt;BR /&gt;&lt;BR /&gt;There are no known problems with this patch as far as I know. But HP would be happy to assist you, drilling this down.&lt;BR /&gt;&lt;BR /&gt;I guess when you say that you "updated" sap.config from /opt/cmcluster/sap/SID, you did not copy it over.. This would be a bad idea as sap.config in the staging area is just a template. But if you did probably nothing would have worked anymore. &lt;BR /&gt;&lt;BR /&gt;Carsten</description>
      <pubDate>Fri, 13 Feb 2009 07:26:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sgesap-problems-with-phss-38923/m-p/5156779#M671516</guid>
      <dc:creator>Carsten Krege</dc:creator>
      <dc:date>2009-02-13T07:26:29Z</dc:date>
    </item>
    <item>
      <title>Re: SGeSAP problems with PHSS_38923</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sgesap-problems-with-phss-38923/m-p/5156780#M671517</link>
      <description>Bonjour Carsten,&lt;BR /&gt;&lt;BR /&gt;You are right : I have not copied ASIS the updated sap.config ;-)&lt;BR /&gt;&lt;BR /&gt;Well, I am afraid I will not place a call to HP. We are supposed to migrate and update the old SAP to the new one this WE and I will have no time for that. So I did a rollback after I opened this thread.&lt;BR /&gt;&lt;BR /&gt;Do you think that if I post some configuration files, you could help ?&lt;BR /&gt;&lt;BR /&gt;Eric</description>
      <pubDate>Fri, 13 Feb 2009 08:22:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sgesap-problems-with-phss-38923/m-p/5156780#M671517</guid>
      <dc:creator>Eric SAUBIGNAC</dc:creator>
      <dc:date>2009-02-13T08:22:25Z</dc:date>
    </item>
    <item>
      <title>Re: SGeSAP problems with PHSS_38923</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sgesap-problems-with-phss-38923/m-p/5156781#M671518</link>
      <description>As previously said, problem gone away when reverting back to SGeSAP scripts delivered with initial release of SGeSAP. No time to investigate and understand ... :-( May be next time.</description>
      <pubDate>Mon, 02 Mar 2009 09:35:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sgesap-problems-with-phss-38923/m-p/5156781#M671518</guid>
      <dc:creator>Eric SAUBIGNAC</dc:creator>
      <dc:date>2009-03-02T09:35:15Z</dc:date>
    </item>
  </channel>
</rss>

