Re: Mirroring redo log groups or not ?
- From: Guillermo Alan Bort <cicciuxdba@xxxxxxxxx>
- To: mwf@xxxxxxxx
- Date: Tue, 7 Apr 2009 23:04:06 -0300
Since I manage databases on many platforms, one of which is windows,
the thing I noticed is that most oracle logs are .log (alert) .trc
(trace files) and config files are .ora I usually create an
association to open these files with a text editor (not always notepad
since they might get quite big) and so have the policy of *never*
naming *any* database file (with the only exception of spfile) with
.ora/.log extension.
On the other hand, we usually have sperate filesystem (on unix, not
always on windows) for different file types (for instance:
a filesystem mounted on /u01 for $OH, a filesystem on /u02,/u03 and
/u04 (each) for data and redo log files and a filesystem on /u98 for
archive and /u97 for admin structure (dump dests and audit dest). So,
basically, if there is something in /u0(2|3|4) that doesn't belong to
any database, it gets deleted. We have different filesystems for
export and disk backup. So, there is no need to manually 'cleanup' the
places where oracle files exist. $OH *should* be static as well, but
it's a little harder to keep track of it.
Kind regards.
Alan Bort
Oracle Certified Professional
On Tue, Apr 7, 2009 at 9:35 PM, Mark W. Farnham <mwf@xxxxxxxx> wrote:
> This calls for analysis. Now why exactly were there copies of the redo logs
> on a drive shared with dynamically extending logs?
>
>
>
> Hmm. Were perchance the “primary” copies of the logs on a properly allocated
> database file system with no competition from things not database, but
> someone decided it would be “safer” to have multiple members in the log
> groups? Unfortunately the only place to put the extra members was a bad
> place.
>
>
>
> But you let that fellow retain access to your production systems? I hope
> retraining was involved, though often the shock of the experience is taken
> for training enough. I would not want to go hunting with such a person.
>
>
>
> mwf
>
>
>
> ________________________________
>
> From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
> On Behalf Of Kenneth Naim
> Sent: Tuesday, April 07, 2009 7:50 PM
> To: mwf@xxxxxxxx; david.barbour1@xxxxxxxxx; Jon.Crisler@xxxxxxx
> Cc: 'Rajeev Prabhakar'; 'Oracle-L Freelists'
> Subject: RE: Mirroring redo log groups or not ?
>
>
>
> I’ve had an admin “cleanup” a filesystem that was filling up by removing all
> *.log files, since the other redo file were on separate filesystems we were
> protected and so was his job. We also name our redo logs with a .ora
> extension now.
>
>
>
> Ken
>
>
>
> ________________________________
>
> From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
> On Behalf Of Mark W. Farnham
> Sent: Tuesday, April 07, 2009 7:04 PM
> To: david.barbour1@xxxxxxxxx; Jon.Crisler@xxxxxxx
> Cc: 'Rajeev Prabhakar'; 'Oracle-L Freelists'
> Subject: RE: Mirroring redo log groups or not ?
>
>
>
> There is no protocol that can protect you from human error by someone with
> authority to remove an online log file.
>
>
>
> I’d actually be surprised if there was someone dumb enough to remove active
> online logs and not anal enough to remove all the copies. But we’ll never
> know, because you’re positing that the folks who removed single member log
> groups would have been saved by multiple members. Unless you have a time
> machine, you cannot test that.
>
>
>
> Regards,
>
>
>
> mwf
>
>
>
> ________________________________
>
> From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
> On Behalf Of David Barbour
> Sent: Tuesday, April 07, 2009 2:22 PM
> To: Jon.Crisler@xxxxxxx
> Cc: Rajeev Prabhakar; Oracle-L Freelists
> Subject: Re: Mirroring redo log groups or not ?
>
>
>
> Mirroring protects you from more than disk failure, it also protects you
> from human error. Please, mirror your logs. There is a long history
> littered with un-employed DBAs backing this recommendation.
>
> <snip>
>
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
