Re: Inheriting a "interesting" recovery process

On 04/08/06, Jared Still <jkstill_at_gmail.com> wrote:
> On 8/4/06, Guerra, Abraham J <AGUERRA_at_amfam.com> wrote:
>
> >
> > Your very best friends are: 'Cold Backup' (hot whenever you can't do
> > colds) and make sure your database is in archivelog mode if you want
> > full recovery...
>
>
> Please explain why a cold backup is necessary.
>

Clearly you have never heard a system administrator utter the phrase: "But, they were only logfiles. We needed to clear some space." coupled with "We don't backup logs."

With a cold backup you *know* that you can get the database back in a working state, even if some sysadmin has gone nuts and earned themselves a place in a large body of water encased in chicken wire with some heavy weights for company.

I've not yet utterly seen a database lost due to a hardware failure or software bug, I've seen several utterly lost due to sysadmin 'error'. In each case the root of the problem has been that sysadmins have had control of the Oracle servers (because management didn't want Oracle DBAs doing sysadmin work) and have messed in the Oracle directories (or fiddled with the backup jobs) without first consultign the DBAs.

Stephen

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

http://stephensorablog.blogspot.com/

 'nohup cd /; rm -rf * > /dev/null 2>&1 &'
--
http://www.freelists.org/webpage/oracle-l