on 2009 Jan 26 7:21 AM
Hi,
Anyone has experience or suggestion on performing SAP ERP60 upgrade on HP MCSG (ServiceGuard)Cluster ? is it better to do it on Clustered or Non-Clustered mode? (as the hostname will be different from clustered and non-clustered mode)
Thanks in advance,
best regards,
Hery
Hi
We have done plenty of then on service guard clusters. We always did them in clustered mode. I don't see a reason, doing it the other way. So just specify the virtual name for the SAP SYSTEM HOST and DATABASE HOST. You might consider deactivating the automatic package switch (cmmodpkg -d). After the upgrade you should manually check the environments of the sidadm user on all nodes and perform a switch test.
Best regards, Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Michael,
Thanks for your helpful feedback.
Anyway, any additional file (e.g. kernel files) beside of from standard upgrade tool need to be applied on the ServiceGuard tool?
Thanks..
Best regards,
Hery
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As i said, i recommend deactivating the automatic package switch during the upgrade. Nothing else has to be done. All i said so far is true for SG on hp-ux, but i am pretty sure it applies for linux as well.
It might help if you talk to your hp contact as well, maybe they want to verify the SG and Serviceguard Extension for SAP versions. HP will have to share a bunch of experiences with upgrades themselves.
Regards, Michael
Hi Michael,
Thanks for your reply.
Anyway, did you run it with Downtime Minimize or Resource Minimize?
Any special action need to be done for Shadow Instance installation on Cluster Mode (comparing Non-Cluster) ?
Best regards,
Hery
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi again
We ran all upgrades with the downtime minimized option. As long as you don't switch, nothing special has to be done. We never had to switch a package though. If you switch during the upgrade, you certainly will need to manually restart the shadow instance and to verify the profiles and user environnements.
Your upgrade directory will need to be included into the package (i can tell you it wasn't in our cases). I just did a short check on /etc/services, but it does not look like the current upgrade is adding the shadow message service anymore. Previous upgrades used to add this:
sapmsSHDSID 3610/tcp
Best regards, Michael
User | Count |
---|---|
70 | |
9 | |
8 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.