Re: Database Outages - Best Practices

Michael,

"Quarterly Security Patchsets".
run with it.
there's 4 maintenance windows a year that they would be foolish not to agree to, even if you don't end up applying patchsets that aren't required.

"Unplanned downtime is becoming almost impossible to plan or get approved".

To me, truly unplanned downtime doesn't really get scheduled, it just "Happens" like the proverbial bumper sticker from decased ago.

Paul

On Mon, 14 Feb 2005 14:32:31 -0600, Michael Fontana <mfontana_at_verio.net> wrote:
>
>
> I was asked to put together a proposal for regularly scheduled outages to
> perform database maintenance. At this time, my company does not have
> scheduled outages, and unplanned downtime is becoming almost impossible to
> plan or get approved.
>
> If anyone has a "best practices" document that can be shared or referenced,
> that would be greatly appreciated. I have worked in several top fortune 500
> companies, so we are looking to implement policies similar to those.
>
> Keep in mind that my management actually doesn't buy the need for outages AT
> ALL. I will need to do a little selling here.
>
> I would be curious to hear of other company's practices, as well as
> vignettes about what one must go through to prepare and implement an outage.
>
> --
> http://www.freelists.org/webpage/oracle-l
>

-- 
#/etc/init.d/init.cssd stop
# f=ma, divide by 1, convert to moles.
--
http://www.freelists.org/webpage/oracle-l