Stopping ServiceGuard for patching SAP

[NHL]

Hi folks,

I need to patch SAP/Oracle on a HPUX cluster but unfortunately I have never worked with ServiceGuard before.

My plan is to stop service guard on all nodes:
# cmhaltcl

Then stop SAP/Oracle, do the SAP upgrade, restart SAP/Oracle. Now restart the cluster:
# cmruncl

Does this sound like a solution that would work ? My priority is having the cluster working correctly when I leave.

Unfortunately I won't have access to the cluster until I get to the clients site, and Im still trying to get info regarding how the cluster is setup and the ServiceGuard version.

Any advice anyone could offer will be much appreciated.

Many thanks,
Nick .

[AL Shehhi]

well ,

Firstly ,

always i like to take some information about the syetem especially the mounted filesystem so i don't miss any one later after finishing the upgrade , maybe one file ssystem will not be mounted for any reason

do

$ bdf > /filesystems


then

check the services packages you have and where each package is mounted by

$ cmviewcl


then ,

stop the cluster

$ cmhaltcl

do your upgrade then ,

$cmruncl

then check the cluster status again ,

$ cmviewcl

don't forget to enable autofailover for each package by :

$ cmmodcl -e packagename.

this just basic information

[Murat SULUHAN]

Hi Nick

You should not stop ServiceGuard package with cmhaltcl.

You should only stop SAP/Oracle applications while package is open (you must see you package is running in cmviewcl output), and then apply patch, then start the applications.

Best Regards

[NHL]

Thanks for your responses.

There seems to be a differing of opinion tho :)
From your posts it seems I should do the following:

1)
# cmviewcl > /tmp/cluster.info
# cmhaltcl
[ Stop SAP/Oracle and do my upgrades ]
[ Start SAP/Oracle ]
# cmruncl
# cmviewcl > /tmp/cluster2.info
Compare the cluster.info files.

Or do I need to :

2)
Stop the SAP/Oracle packages
# cmhaltpkg
[ Stop SAP/Oracle and do my upgrades ]
[ Start SAP/Oracle packages ]
# cmrunpkg

So should I do 1) or 2) or neither of the above ?

Thanks
Nick .

[Murat SULUHAN · Accepted solution]

Hi Nick

I have no idea about your installation but
If your Oracle/SAP installation is in your shared drive (not local system disk) and if you stop your package with cm* commands you cannot see your Oracle/SAP mounts. Because cm* command s stop your application then unmount shared drive.

So If you just stop your Oracle/SAP, you can apply patch safely, these solution valid for both case, I mean Oracle/SAP in shared drive or local disk.

and another issue you must patch both Oracle/SAP application, if your installation is in your local disk.

Best Regards

[NHL]

Thanks again.

So if SAP/Oracle use a shared drive then I must NOT run any cm commands to stop the package or the cluster. I just stop the applications and install the patch on any node as if there was no cluster ?

If they're not on a shared drive I can cmhaltpkg, stop the app, patch, start the app, cmrunpkg ?

Just looking for a bit more clarification :)

[Murat SULUHAN]

In fact lots of Oracle patches applies some sql commands on your data so I don't recommend shutdown the package, because generally oracle data is in your shared drive. I am not good at SAP but I think its patches like Oracle.

So if you shutdown the package you cannot access your Oracle datafiles, therefore if the patch wanted to access your datafiles it will fail.

So my opinion is you should not shutdown package just shutdown your application if you want to patch your ServiceGuard packaged application.

Best Regards