SGeSAP problems with PHSS_38923

[Eric SAUBIGNAC]

Bonsoir,

Has someone tested latest scripts delivered with PHSS_38923 "SGeSAP B.04.51.00 Cumulative Patch" ?

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 ].

By chance, database is correctly stopped. Most important !

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.

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 ?

I guess I will do a rollback, but I would like to understand before giving up :-(

Eric

[Carsten Krege]

It is hard to identify the problem w/o package logs. I really suggest you open a call with HP Support.

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.

There are no known problems with this patch as far as I know. But HP would be happy to assist you, drilling this down.

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.

Carsten

[Eric SAUBIGNAC]

Bonjour Carsten,

You are right : I have not copied ASIS the updated sap.config ;-)

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.

Do you think that if I post some configuration files, you could help ?

Eric

[Eric SAUBIGNAC]

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.