Re: Planned Maintenance - Believe or not ?

From: Andrew Kerber <andrew.kerber_at_gmail.com>
Date: Fri, 22 Jun 2012 12:41:01 -0500
Message-ID: <CAJvnOJYTO8qmtzJ_6sveCygH0QOSmS0q_0KTdZ44D3_ZY9XJkg_at_mail.gmail.com>



Joel-
Not starting an argument hear, but you should realize that most planes requires several hours of ground maintenance for every hour of flight, and fighter jets are among the worst in that regard. That being said, I have to agree that in this day and age there is no reason why you need to have regularly scheduled outage windows except for patches and stuff. And if you dont patch, you really shouldnt need much downtime. I have a little Linux server I run emails on, on a cheap 2g commodity motherboard that has been running without problem for 5 years or so without a reboot. Other than the time or two we lost power at my house.

On Fri, Jun 22, 2012 at 11:56 AM, <Joel.Patterson_at_crowley.com> wrote:

> 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_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
> 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
> --
> http://www.freelists.org/webpage/oracle-l
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

-- 
Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'


--
http://www.freelists.org/webpage/oracle-l
Received on Fri Jun 22 2012 - 12:41:01 CDT

Original text of this message