Re: Dataguard / Archive Logs

  • From: David Sharples <davidsharples@xxxxxxxxx>
  • To: cjpengel.dbalert@xxxxxxxxx
  • Date: Wed, 1 Jun 2005 16:19:30 +0100


I have a couple more questions on this as its getting quite involved
here as to how we are going to set it up.

Still in the planning phase here and what we have is the primary and
seconday site each with its own SAN.

The SAN's are connected via a fibre link wihich have their own
transfer protocol between them.  At the moment there is no standard
network connection available between the two sites for us.

As the data gets written on the primary, the SAN is replicating that
data automatically to the standby site so in theory they are the same

so all being well can we then take that archive log and apply it
manually to the standby database.

Is this a known configuration? =20

This is going to be harder to do a test on, so if anyone knows I would
be extremely grateful

On 5/31/05, Carel-Jan Engel <cjpengel.dbalert@xxxxxxxxx> wrote:
> It depends.
> If using LGWR to get the redo sent to the standby (using standby redo log
> files), the logswitch will be performed locally on the standby. So, there
> is no incomplete archived redo logfile at the standby.
> A test for the first case can go along the following steps:
> - stop the log-transfer (defer the log_archive_dest_x)
> - perform a logswitch on the primary.
> - Copy the archived logfile to the standby manually
> - blank or delete the last blocks, eg using dd. (talking *n*x here)
> - register the logfile manually to the stanby
> - try to apply it.
> - see what happens

Other related posts: