RE: Inheriting a "interesting" recovery process
- From: "Cary Millsap" <cary.millsap@xxxxxxxxxx>
- To: <Rich.Jesse@xxxxxx>, <stephenbooth.uk@xxxxxxxxx>, <jkstill@xxxxxxxxx>
- Date: Fri, 4 Aug 2006 12:51:05 -0500
I would agree that .log is a dangerous extension for files that you want
*not* to get picked off by some SA's "find" command for deletion.
And the OFA spec definitely does NOT put data files beneath ORACLE_BASE
or ORACLE_HOME (http://www.hotsos.com/e-library/abstract.php?id=19).
So I agree with you on both accounts.
For what it's worth.
Cary Millsap
Hotsos Enterprises, Ltd.
http://www.hotsos.com
Nullius in verba
Hotsos Symposium 2007 / March 4-8 / Dallas
Visit www.hotsos.com for curriculum and schedule details...
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jesse, Rich
Sent: Friday, August 04, 2006 12:41 PM
To: stephenbooth.uk@xxxxxxxxx; jkstill@xxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: RE: Inheriting a "interesting" recovery process
Which is precisely why I break this OFA rule and name every Oracle DB
file with a ".dbf" extension. It eliminates the confusion of the dual
meaning of the term "log" for the archived logs, making it a simple rule
to let the SAs know that ".dbf" files are important
don't-touch-without-asking Oracle files. Even before taking my first
Oracle DBA class the ".log" naming jumped out at me.
As I've said before, I do like the vast majority of the structure of
OFA, but this and having the datafile mountpoint under ORACLE_BASE (or
is it ORACLE_HOME?) are two that I think are asking for trouble.
Rich
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of stephen booth
Sent: Friday, August 04, 2006 9:33 AM
To: jkstill@xxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: Inheriting a "interesting" recovery process
On 04/08/06, Jared Still <jkstill@xxxxxxxxx> wrote:
> On 8/4/06, Guerra, Abraham J <AGUERRA@xxxxxxxxx> 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
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
