Copying archived redo logs to a standby site
Prior to Oracle8i, copying of archived redo logs from the primary to the standby site
was not automated. You were free to use any method to copy the files across the network.
For example, you could schedule a batch job that copies archived logs to the
standby site every N minutes. If the primary site fails, these copies would limit the
lost redo information (and therefore the lost data) to a maximum of N minutes of
work plus whatever was in the currently active log.
Oracle8i first provided support for the archiving of redo logs to a destination on the
primary server as well as on multiple remote servers. This feature automates the
copying and application of the archived redo logs to one or more standby sites. The
lost data is then limited to the contents of any filled redo logs that have not been
completely archived, as well as the current online redo log. Oracle also automatically
applies the archived redo logs to the standby database as they arrive.
Oracle9i added the option to specify zero data loss to a standby machine.
Pages:
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622