RE: Duplexing Archived Log Files

From: Jack C. Applewhite <japplewhite_at_inetprofit.com>
Date: Thu, 06 Dec 2001 15:00:43 -0800
Message-ID: <F001.003D6E2E.20011206144524@fatcity.com>

Dennis,

We use

log_archive_dest_1
log_archive_dest_2

sending a copy of each archived redo log to our Standby database
(log_archive_dest_2).

log_archive_dest_2 is used with the OPTIONAL parameter, since we don't want to stop archiving if the Standby is down or there's some problem with the LAN. We also have
log_archive_min_succeed_dest = 1
to make sure that the archiving succeeds at least to the local target drive
(log_archive_dest_1).

It's worked great for us (8.1.6.0.0 EE under Win2k).

BTW, we use RMan for hot backups and like it very much. We can also issue the Alter Tablespace Begin Backup command and get instantaneous results - which I had to do recently to restore some datafiles to the Standby after one of its disks failed. I wonder why you get such slow response?

Jack

Jack C. Applewhite
Database Administrator/Developer
OCP Oracle8 DBA
iNetProfit, Inc.
Austin, Texas
www.iNetProfit.com
japplewhite_at_inetprofit.com
(512)327-9068

-----Original Message-----
WILLIAMS
Sent: Thursday, December 06, 2001 12:29 PM To: Multiple recipients of list ORACLE-L

Is anyone using the LOG_ARCHIVE_DUPLEX_DEST parameter? Any problems with it?

We are on Oracle 8.1.6 on Compaq Tru64. On our ERP 150-gig. database, we are currently doing a cold backup weekly. This means that we are very dependent on archive logs.

Recovery time isn't a big concern. In the event of a failure, recovery time isn't that critical. Loss of a week of work would be.
We have tried hot backups successfully on smaller databases, but we found that once we issue ALTER TABLESPACE BEGIN BACKUP there was often a delay of hours for that command to complete. So we gave up on hot backups.
We are starting to work with RMAN and feel in the long run this will be an ideal solution. Thanks to everyone for answering my newby RMAN questions.
Recently Oracle has added a feature to duplex the archive log files. This sounds like it would lessen our archive log vulnerability. However, it causes my sys admin more work, so I would appreciate some feedback before I add this burden to his work. Thanks for any thoughts you care to share. Dennis Williams DBA Lifetouch, Inc. dwilliams_at_lifetouch.com

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Jack C. Applewhite
  INET: japplewhite_at_inetprofit.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L


(or the name of mailing list you want to be removed from).  You may

also send the HELP command for other information (like subscribing).

Received on Thu Dec 06 2001 - 17:00:43 CST