Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Database Outages - Best Practices

RE: Database Outages - Best Practices

From: Hollis, Les <>
Date: Mon, 14 Feb 2005 15:33:10 -0600
Message-ID: <>

As far as prep,

We set out a timeline and an implementation doc as to what we will be doing ..

timeline includes times and content of notification pages to be sent, when we start backup prior to window, verification of backup success, completion of BCV copy and the fact that the BCV copy database opens successfully.

Steps we will be performing at what time (these are approximate times).

When we will complete and the page to be sent, verification by Apps support that the application does indeed function as advertised and final page of completion of maintenance window....DB ready for use

Implementation doc states the general purpose of maintenance who is involved, contact names and numbers, what t5ables are affected, any new init.ora parameters, new users to create, new DB links, etc

-----Original Message-----
[] On Behalf Of stephen booth Sent: Monday, February 14, 2005 3:16 PM
Cc:; Subject: Re: Database Outages - Best Practices

On Mon, 14 Feb 2005 20:38:11 +0000, <> wrote:
> most outages are typically related to builds. your adding tables,
dropping tables, data migration, or the application is deploying a new version.
> standard is outside of regular business hours. negotiate notice in
advance. Negotiated frequency. Negotiated downtime. Negotiated notification process if there is a delay in bringing the system back up. >=20
> you want it all written down in advance, with appropriate phone
numbers and you want a client signature.

Ditto on all of the above.

One useful way I've found of getting management to agree outages is to not call them outages. Call them 'Power Possession'. A power possession is a period when you or any of the other techs and engineers associated with a system (database, OS, hardware, network, power, building management &c) have the option or downing the system, the datacentre or even the network for maintenence.

Schedule them well inadvance (try for a year), as frequently as possible, for times time the system isn't busy and for a good long period of time. Most times you won't need them and will be able to tell the business "It's OK, we don't need to take the service down, this time". When work needs to be done try to get as much non-interfering work into that window as possible (obviously don't try to upgrade the OS and database software at the same time but you should be OK working on the database whilst a network switch is being=20 upgraded or after a test firing of the backup generators (always make sure that your backup generators are test fired on the manufacturers reccommended schedule, this is the voice of bitter experience speaking), for example).

It's better to ask a silly question than to make a silly assumption.


Received on Mon Feb 14 2005 - 16:33:43 CST

Original text of this message