Re: Dataguard secondary archive apply

On Mon, 2006-08-07 at 16:56 -0400, David Barbour wrote:

> First, as folks have suggested, you need to have(as a minimum) the
> following parameters in the init<SID>.ora file on the primary and
> standby:
>
> On the Primary:
>
> # ==========
> # Parameters for DataGuard/Standby database
> # ==========
>
> log_archive_dest_1 = 'LOCATION=<Primary Archivelog Destination>'
> log_archive_dest_2 = 'SERVICE=<Standby SID>'
> log_archive_dest_state_1 = enable
> log_archive_dest_state_2 = defer # Change to enable after
> confirming standby destination is valid
>
> remote_archive_enable = true
>

So far, no problem. 'Remote_archive = send' is a way to prevent a primary from accidently receiving archives when a standby is started as a second primary.

> fal_server = PR1
> fal_client = DR1
> standby_archive_dest='<Standby Archivelog Destination>'

The last three parameters are bound to the standby. They don't need to be specified on the primary.

> standby_file_management = auto #Optional - but very handy

Agree.

>
> On the Standby:
>
> # ==========
> # Parameters for DataGuard/Standby database
> # ==========
>
> log_archive_dest_1 = 'LOCATION=/oracle/PR1/oraarch'
> log_archive_dest_state_1 = enable
>
> remote_archive_enable = true

Or remote_archive = receive

>
> fal_server = PR1
> fal_client = DR1
> standby_archive_dest='/oracle/PR1/oraarch'
> standby_file_management = auto
>

Best regards,

Carel-Jan Engel

===
If you think education is expensive, try ignorance. (Derek Bok) ===

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