Re: Duplex Archive Logs

We currently use duplexed archive logs. When log_archive_min_succeed_dest
is set to 2, the ARCH process must successfully write both logs to their respective destinations or it will fail and your DB will hang. When it is
set to 1, only one of the destinations must succeed. I had a small 2 GIG
harddrive on a test DB (where the duplexed archive log went) fill up and Oracle disabled logging to that dest, notified me via the trace files, and
kept archiving to the main destination. I am assuming you have archiving
turned on and are getting archived log files in the main destination. If
not, there is another init.ora parameter, log_archive_start = TRUE, which
automatically turns archiving on for the db. If this isn't in the init.ora
file, you have to manually turn archiving on at the svrmgr prompt. Hope this helps.

Joe Long

Dennis Flinn wrote:
>
> I was wondering if anyone has worked with duplexed archive logs. In
> reading the documentation about the parameters it appears that you have
> to set two parameters in the init.ora. First, the
> log_archive_duplex_dest, I then left the log_archive_min_succed_dest set
>
> to the default of '1'. After I recycled the database I forced a log
> switch and found the archive log was not written into the duplex
> location. I haven't done any further testing but after reading the
> documentation again it stated that if log_archive_min_succed_dest is set
>
> to '1' then the write to log_archive_duplex_dest is a "best effort".
> I'm not sure what that means. Like I said I haven't had the chance to
> set the log_archive_min_succed_dest to '2'. But does "best effort" mean
>
> if the server can write to log_arch_dest then if will not write to
> log_arch_duplex_dest? I guess that brings up another question. If I
> setup a duplex_dest and leave min_succed set to '1' - if the
> log_arch_dest fills up will the archive logs then switch over to
> duplex_dest with the database hanging?
Received on Thu Sep 02 1999 - 08:54:35 CDT