To stop the redo application in a physical standby database??”
whether in a background session or a foreground session??”use the following command:
alter database recover managed standby database cancel;
For a logical standby database, the command to stop the Log Apply Services is
alter database stop logical standby apply;
Managing Gaps in Archive Log Sequences
If the standby database has not received one or more archived logs generated by the primary
database, it does not have a full record of the transactions in the primary database. Oracle Data
Guard detects the gap in the archive log sequence automatically; it resolves the problem by
copying the missing sequence of log files to the standby destination. Prior to Oracle 10g, the FAL
(Fetch Archive Log) client and server were used to resolve gaps from the primary database.
To determine if there is a gap in your physical standby database, query the V$ARCHIVE_GAP
view. For each gap, that view will report the lowest and highest log sequence number of the set of
logs that are missing from the standby database. If there is some reason why Oracle Data Guard
has not been able to copy the logs, you can copy the files manually to your physical standby
database environment and register them using the alter database register logfile filename command;
then you can start the redo apply process. After the logs have been applied, check the V$ARCHIVE_
GAP view again to see if there is another gap to resolve.
Pages:
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739