patches that required a reboot

[A.K.]

hello all,
I have a production server and I need to install some patches that required a reboot .
Currently, I can not reboot the server.
Can I install the patches and specify autoreboot=false and than leave it as is until I have the opportunity to reboot.
Is it safe?
What are the risks?

[Patrick Wallek · Accepted solution]

Nope. If you specify autoreboot=false, I don't think the patches will install at all.

The best bet is to wait until your reboot window to install the patches. The patches won't really do you any good until you reboot anyway.

[Raj D.]

Hi A.K ,

Kernel patches definitely required a reboot.

If you are installing kernel patch , i.e PHKL_XXXXX , needs a reboot , What patch are you going to install. !

cheers,
Raj.

[DCE]

It would not be a good idea to instal these patches and not reboot.

Depending on the patch, your system, while still running, could be in an unstable state. Kernel parameters are not in sync with those the system last booted from, for example. The output from a system in this state is not reliable.

In fact the system may very panic and reboot on you anyway.

[Rick Garland]

Never tried it but all I've heard is that the autoreboot=false does not work with patches that require reboot - the system will reboot anyway.

Going through SAM you can wait to click the button but reboot is required.

Waiting to boot after installing patches (that require reboot) can make the system unstable.

[A.K.]

OK , got the message I will not install until I can reboot.
Thanks
A.K.

[Torsten.]

If you have several patches and each of them requires a reboot, then swcopy all patches to a new depot an install all at once from your new depot.
You have to reboot your server only once instead of several times and you'll save time.

T.

[Manoj Sivan]

Hi there,

All kernel patches require reboot and if we specify autoreboot=false.swinstall will not apply those patch and it will terminate the install.

cheers

manu

[Bill Hassell]

Patches are often replacements for critical components and many are very dependent on each other. If you patch a few files (drivers, libraries, etc), the kernel could potentially use one of the updated files without proper configuration and crash your server. This is potentially very serious because your system may not reboot due to an incomplete patch sequence.

You must schedule downtime for the server, then run an Ignite/UX backup, install your patches and let the server reboot. If you do not have a test system, you do run a small risk of incompatibility with your application after you reboot. The solution is to setup MC Service Guard as well as a test system to verify operation after patching.

[Mahesh Kumar Malik]

Hi AK

It is not a preferred option. Kernel patches (PHKL_XXXX) require reboot. You may schedule system shutdown and then apply such patches.

Regards
Mahesh