Re: max_failure and noreopen parameter in dataguard?

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?

--
http://www.freelists.org/webpage/oracle-l