|
Install Fixpack without stopping applications
|
|
Replies:
3
-
Pages:
1
-
Last Post:
Oct 20, 2009 10:05 AM
Last Post By: thomas.quadflieg
|
Threads:
[
Previous
|
Next
]
|
|
Posts:
5
Registered:
Nov 18, 2008 11:56:40 AM
|
|
|
|
Install Fixpack without stopping applications
Posted:
Oct 20, 2009 05:41:03 AM
|
|
|
|
Hello there,
according to the "Installation and Configuration Guide" you have to stop all applications with samctrl -u a <node> and stoprpnode before installing a MP fixpack. I thought of an method to update MP without touching the applications:
1. samctrl -M T
2. stoprpnode -f
3. install Fixpack
4. startrpnode (in single-node cluster: startrpdomain)
5. samctrl -M F
I tested these steps in a single node cluster and it worked. But, regarding the stoprpnode -f option, I am not sure if this update-method is not too risky. Do you see any risks by updating MP with this method?
Are there other alternatives for updating MP without touching the applications?
Regards,
Thomas
|
|
Posts:
5
Registered:
May 12, 2009 09:51:00 AM
|
|
|
|
Re: Install Fixpack without stopping applications
Posted:
Oct 20, 2009 08:31:19 AM
in response to: thomas.quadflieg's post
|
|
|
|
Hello Thomas,
using stoprpnode -f is risky because it is executed regardless if any resource can be brought offline correctly or not (hence the "force" option). I would not recommend this in a production environment. It is usually best to stick to the procedure described in the manual to avoid data loss or similar problems.
Regards,
René
|
|
Posts:
38
Registered:
Jun 18, 2008 03:37:07 AM
|
|
|
|
Re: Install Fixpack without stopping applications
Posted:
Oct 20, 2009 08:37:08 AM
in response to: thomas.quadflieg's post
|
|
|
|
Hello,
the potential problem with 'stoprpnode -f / stoprpdomain -f' is the critical resource protection: If a critical resource is running on a node that is stopped, the node is usually rebooted using the softdog or dead man switch to prevent the resource from being running on more then 1 node at any time. So I would expect that 'stoprpnode -f' results in a crash of the node in case a critical resource is currently running.
A critical resource is defined with the value of the attribute ProtectionMode - a value of 1 means critial, 0 means non-critical. Examples for critical resources are resouces of class IBM.ServiceIP, or filesystems.
You should be able to use 'stoprpdomain -f' to stop the domain without stopping the resources, however I recall that it did not work for some RSCT levels, so you should test the SA MP level carefully on a test system before using the command on productive systems.
Enrico Joedecke
|
|
Posts:
5
Registered:
Nov 18, 2008 11:56:40 AM
|
|
|
|
Re: Install Fixpack without stopping applications
Posted:
Oct 20, 2009 10:05:25 AM
in response to: Enrico_Joedecke's post
|
|
|
|
Thank you for your answers, I worried that RSCT could spoil this idea.
Regarding the solution with stoprpdomain -f it would be interesting to know how detailed the command should be tested. Can I assume, that it works for those RSCT levels where a test was succesfully one-time? Or can it work from time to time depending on the actual config-state?
|
|
|
|
|
