RE: Planned Maintenance - Believe or not ?

  • From: "Lange, Kevin G" <kevin.lange@xxxxxxxxxx>
  • To: <Oracle-L@xxxxxxxxxxxxx>
  • Date: Fri, 22 Jun 2012 12:49:52 -0500

 Our windows app servers are setup such that we take a couple out of
rotation to do the patching so we are not down from the users point of
view.

RAC systems on solaris servers take rolling outages, so , again, from
the user point of view, they are up.

The "In-Place" patches are everything between those.  Depending on the
schedule of the large maintenance releases, things can stay up longer
these days than they did, say, 10 years ago.

-----Original Message-----
From: Uzzell, Stephan [mailto:SUzzell@xxxxxxxxxx] 
Sent: Friday, June 22, 2012 12:40 PM
To: Lange, Kevin G; Oracle-L@xxxxxxxxxxxxx
Subject: RE: Planned Maintenance - Believe or not ?

Kevin,

I like the idea of this, but... We're a windows shop. If we don't stay
on top of the various OS security patches and updates, we would probably
not be within PCI compliance. So we have monthly maintenance windows to
apply the latest patches, some of which require reboots...

To minimize this, we have services configured in most (not yet all)
environments; we are working on a strategy of rolling outages - stop the
services on node 1 so no future connections come into it, all new
connections go to node 2 (or 3/4 in our larger RACs), when all (well,
most) connections to node 1 have dropped (from users logging off, for
example), we can take node 1 fully down and patch, reboot, &c. Bring it
back up, start the services, move on to the next node. Rinse and repeat.
We can mostly avoid any outage to our customers this way, but we have
not found any way around the periodic reboots, and the effects on the
local instance (which is what the original question seemed to be about -
rather than customer impact).

Stephan Uzzell

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Lange, Kevin G
Sent: Friday, 22 June, 2012 13:27
To: Oracle-L@xxxxxxxxxxxxx
Subject: RE: Planned Maintenance - Believe or not ?

I agree with Joel.  24x7x365 .  Unless there is a degredation , I really
see no reason to take things down.  Especially with most of the patches
on various things being "In-Place" patches these days.

That being said, I still like a nice cold backup of a database now and
again.   Maybe its just because of doing this so long that you remember
the times when it was essential to have those backups.   I don't know.
It just gives me a warm, fuzzy feeling to know I have it.

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of
Joel.Patterson@xxxxxxxxxxx
Sent: Friday, June 22, 2012 11:56 AM
To: sreejithsna@xxxxxxxxx; Oracle-L@xxxxxxxxxxxxx
Subject: RE: Planned Maintenance - Believe or not ?

I run single instances, for quite awhile, and with several companies and
OS's.   For oracle databases, my analogy is that it should be treated
like a fighter jet plane.   These planes are built to run 24hours/day
and operate better that way.  They actually require more or completely
different maintenance schedule(s) depending on how long they stay idle.

Analogously, oracle doesn't like to span startups, with things like
historical  reports (Ent mgr), v$ views, and just the extra warm up that
happens upon start up to mention some.  They do get shutdown once in a
while for maintenance reasons, but no schedule.   

In the old days, rebooting was done for various reasons.  Back in the
early 90's, on HP, and Dell, the sysadmins wanted a reboot 'the server'
on Sunday night believe it or not, (thus the databases went
with that).   Even running on windows I did not have a scheduled reboot.


Having said that, some people 'keep' a scheduled window for rebooting
for ease of administration, (whether for the app or server, or database)
-- they always have a window for maintenance and therefore scheduling
the maintenance is easier.

Now applications that run in windows boxes sometimes need it, especially
with mistakes like memory leaks and the like.




Joel Patterson
Database Administrator
904 727-2546

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Sreejith S Nair
Sent: Friday, June 22, 2012 12:34 PM
To: Oracle - L
Subject: Planned Maintenance - Believe or not ?

Hi friends,

The question is about the planned maintenance activities you do on a
server level or database level. The activity I am referring to is
rebooting the node and restarting database instances , crs stack etc. we
had this routine from sometime back, but now management asks why should
we do it. I have heard from many people that they usually do a server
reboot when the uptime goes more than 6 months or so. Now,the management
is saying why we have to do it. The plain explanation is that a software
is designed to run and to handle a load , then it should run for ever if
nothing on it is changed. 

I would like to know whether any one has something like a planned
maintenance activity where you reboot servers and reboot instances every
6 months or so ?

Regards,
Sreejith
-- Sent from my iPhone
--
//www.freelists.org/webpage/oracle-l


--
//www.freelists.org/webpage/oracle-l



This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity to
which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.

--
//www.freelists.org/webpage/oracle-l



This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.

--
//www.freelists.org/webpage/oracle-l


Other related posts: