And multiplexing of online redo logs has, er... precisely what? to do with
running out of space on an archive destination?
HJR
--
----------------------------------------------
Resources for Oracle: http://www.hjrdba.com
===============================
"Jac" <jacxine_at_yahoo.com> wrote in message
news:a4id18$3lo1_at_medusa.qualitynet.net...
> This is something called multiplexing log files. Check the view V$LOGFILE
to
> see how many members are there in each redo log group. It is better to add
a
> member (log file) to each group so as to have a good copy, in case any
hard
> disk fails (or u don't have hardware mirroring). You can add it using the
> ALTER DATABASE ADD LOGFILE MEMBER 'filename' TO GROUP group_number;
> The new member could be in a different directory/drive.
> Multiplexing control files are a little different.
> HTH
> "Tom" <tmar_at_nospamm.nac.net> wrote in message
> news:MPG.16d65b5c8c3f9e1198968f_at_news.supernews.com...
> > Hi,
> >
> > I was wondering if it is possible to distribute archive log files over
> > multiple disks/directories. I'm running version 8.1.6.
> >
> > Every so often we have a job that generates a tremendous amount of space
> > and it can come close to blowing the drive we use for the archive logs.
> > What I'd like to do is have it eitehr alternate between two disks or
> > failover to a second drive if the first gets full.
> >
> > Any help/advise would be appreciated!
> >
> > Thanks,
> > Tom
>
>
Received on Fri Feb 15 2002 - 02:09:15 CST
