From oracle-l-bounce@freelists.org Wed Jan 12 06:53:04 2005 Return-Path: Received: from air189.startdedicated.com (root@localhost) by orafaq.com (8.11.6/8.11.6) with ESMTP id j0CCr3j18315 for ; Wed, 12 Jan 2005 06:53:03 -0600 X-ClientAddr: 206.53.239.180 Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180]) by air189.startdedicated.com (8.11.6/8.11.6) with ESMTP id j0CCr3n18309 for ; Wed, 12 Jan 2005 06:53:03 -0600 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 661E272C47B; Wed, 12 Jan 2005 07:59:39 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02971-91; Wed, 12 Jan 2005 07:59:39 -0500 (EST) Received: from turing (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id B5C8272C7BE; Wed, 12 Jan 2005 07:56:59 -0500 (EST) Message-ID: <015801c4f8ad$4d33fd60$e300a8c0@user12344> From: "Yechiel Adar" To: References: <20050112134151.13E5.KAMUSIS@gmail.com> <1105515329.28292.75.camel@dbalert199.dbalert.nl> <20050112160411.1427.KAMUSIS@gmail.com> Subject: Re: Re[2]: max_failure and noreopen parameter in dataguard? Date: Wed, 12 Jan 2005 15:47:47 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-archive-position: 14664 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-To: oracle-l-bounce@freelists.org X-original-sender: adar76@inter.net.il Precedence: normal Reply-To: adar76@inter.net.il X-list: oracle-l X-Virus-Scanned: by amavisd-new at freelists.org reopen is the interval in seconds between attempts to open, default 300 seconds. max_failure is the number of attempts to reopen, default is nomax_failure meaning infinit attempts. . I think you need: MAX_FAILURE=10 REOPEN=60 That will give you 10 attempts to reopen, with one minute between each attempt. Yechiel Adar Mehish Computer Services ----- Original Message ----- From: "Leyi Zhang" To: "Carel-Jan Engel" Cc: Sent: Wednesday, January 12, 2005 10:09 AM Subject: Re[2]: max_failure and noreopen parameter in dataguard? > is that? > in logical, this REOPEN will never occur, so "MAX_FAILURE=1 NOREOPEN" > seems reasonable. > but, I'll try "MAX_FAILURE=1 REOPEN=10". > Thanks, Carel. > > On Wed, 12 Jan 2005 08:35:29 +0100 > Carel-Jan Engel wrote: > > > The Fine Doc also states that > > "When you specify the MAX_FAILURE attribute, you must also set the > > REOPEN attribute to specify how often archival operations are retried to > > the particular destination" (Oracle Data Guard Concepts and > > Administration Release 9.2, page 12-29, last sentence) > > > > So, it seems that the attributes you use (MAX_FAILURE & NOREOPEN) are > > mutually exclusive. Results are unpredictable ;-) > > > > Best regards, > > > > Carel-Jan Engel > > > > === > > If you think education is expensive, try ignorance. (Derek Bok) > > === > > > > Upcoming appearances: > > > > * Jan 27, 2005: London, UKOUG Unix SIG: Data Guard Best Practices > > * Feb 9-10, 2005: Denver, RMOUG Training Days: Data Guard > > Performance Issues > > * Mar 6-10, 2005: Dallas, Hotsos Symposium: Data Guard Performance > > Issues > > > > On Wed, 2005-01-12 at 06:58, Leyi Zhang wrote: > > > > > My database is Oracle9201 on Solaris 8 > > > I set log_archive_dest_2='SERVICE=ctsdb.standby lgwr async=20480 > > > net_timeout=15 max_failure=1 noreopen' > > > and the size of redofile in primary site is 3M. > > > > > > I run a procedure which insert 600000 records in loop to test this > > > dataguard environment. > > > > > > I unplugged the standby site's network, due to the online document, that > > > the primary site will only check the netwotk once, if failed then never > > > archive to that destination until we reenable it. > > > > > > but in fact, I found primary site always check the network whenever the > > > log switch occured. and I checked the v$archive_dest's STATUS column, > > > the 'log_archive_dest_2' is 'VALID'. > > > > > > After I cancel the procedure, 'log_archive_dest_2' STATUS column in > > > v$archive_dest change to 'ERROR'. > > > > > > But after I replug the network at standby site, I ran "alter system > > > switch logfile;", all the gap archivelog files begin to transfer to the > > > standby site and all seems OK. > > > I thought this is not "noreopen"'s meaning! > > > > > > what did the "net_timeout=15 max_failure=1 noreopen" means on earth? > > > > > > -- > Kamus > > 那么多1G的邮箱,我能用来干什么:-) > A Oracle8i & 9i Certified DBA from China > > -- > http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-l