Thank you all for your input, and thanks to Jeff Herrick for teaching me =
something new about Windows patching.
> -----Original Message-----
> Jeff Herrick
>=20
> Most patches have a 'silent' as well as a 'no-reboot' option. The
> problem is that they are not always the same for all patches so
> you have to run the patch from a command line first with the
> '/?' option to discover them (usually /S and /X but it varies)
>=20
> With these options you can copy the patch to multiple servers
> and then remotely execute using something like PSEXEC from
> SysInternals. After this is done the reboots can be scheduled
> based on a balance between required availability of the server
> and the critical nature or risk exposure of the problem that the
> patch fixes.
>=20
> Of course you should also have tested the patch before rolling it
> out =3D8-0
>=20
> Multiple patches that would normally require a series of reboots can
> be 'chained' together using the QCHAIN program available from the
> Microsoft KB. This way only one reboot of your production server(s)
> is necessary. Note that only QCHAIN has the smarts to determine
> which DLL versions are to be swapped around. If you just strung a set
> of patches together using /quiet /noreboot you risk having a broken
> O/S after the reboot
Please see the official ORACLE-L FAQ:
http://www.orafaq.com
To unsubscribe send email to: oracle-l-request_at_freelists.org
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Received on Thu Feb 12 2004 - 17:56:31 CST
