[Oracle-l] installing security patches on a Windows database server (was "Oracle 10g for Windows")

-----Original Message-----
Mercadante, Thomas F
=20
...
=20
I have windows databases that have been running for 3 years=20
now. *Never*
does the machine crash. And *never* do we reboot "just=20
because we should".
=20
...

-----Original Message-----
Mercadante, Thomas F
=3D20
...
=3D20
I have windows databases that have been running for 3 years=3D20
now. *Never*
does the machine crash. And *never* do we reboot "just=3D20
because we should".
=3D20
...

-----Original Message-----
Mercadante, Thomas F
=20
...
=20
I have windows databases that have been running for 3 years=20
now. *Never*
does the machine crash. And *never* do we reboot "just=20
because we should".
=20
...

On Thu, 12 Feb 2004, Jacques Kilchoer wrote:

I'm sure that with proper management etc. a Windows database server can =
be reliable. But one thing that puzzles me - when you install a =
Microsoft security patch, the dialog box at the end (almost) always says =
"Reboot the machine now." I religiously do that since all of my Windows =
databases can be brought down (they're used for development.) What do =
people do with a production database server?
----------------------------------------------------------------
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
-----------------------------------------------------------------

-----Original Message-----
Mercadante, Thomas F
=3D20
...
=3D20
I have windows databases that have been running for 3 years=3D20
now. *Never*
does the machine crash. And *never* do we reboot "just=3D20
because we should".
=3D20
...

On 02/12/2004 03:04:08 PM, Paula_Stankus_at_doh.state.fl.us wrote:
Don't do the patch until after hours!!!!!!!!!!!!!!!

In addition, when your company has offices in time zones all over the
globe,
the idea of 'after hours' gets a bit muddy.





Mladen Gogala
Sent by: oracle-l-bounce_at_freelists.org
02/12/2004 01:36 PM
Please respond to oracle-l


To: oracle-l_at_freelists.org
cc:
Subject: Re: installing security patches on a Windows database server (was "Oracle
10g for Windows")


On 02/12/2004 03:04:08 PM, Paula_Stankus_at_doh.state.fl.us wrote:

Define "after hours". When working at OXHP, after hours was 2 hours
a week, on Saturday afternoon. Everything that required downtime had
to be done then. Restarting database at any other time required an
explicit approval from the CIO himself or coordination between
VP of shared services, VP of development and representatives of
the business side. Restarting system is actually a very, very big
deal. I know a guy who used to work at the site which managed
911 calls for the state of NY. They had downtime window of 1 hour
a month. The phrase "after hours" can be radically different from
one place to another. For instance, I doubt that Rajendra can
restart database which follows the scores of the sport events
after 5 PM. That would be a bigger scandal then the unrehearsed
wardrobe malfunction during the recent sport mega-event.


----------------------------------------------------------------
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
-----------------------------------------------------------------




----------------------------------------------------------------
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
-----------------------------------------------------------------

-----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

On 02/12/2004 03:04:08 PM, Paula_Stankus_at_doh.state.fl.us wrote:
Don't do the patch until after hours!!!!!!!!!!!!!!!