Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Oracle Data Guard 11gR2 Administration : Beginner's Guide

You're reading from   Oracle Data Guard 11gR2 Administration : Beginner's Guide If you're an Oracle Database Administrator it's almost essential to know how to protect and preserve your data. This is the perfect primer to Data Guard that covers all the bases with a totally practical, user-friendly approach.

Arrow left icon
Product type Paperback
Published in Jun 2013
Publisher Packt
ISBN-13 9781849687904
Length 404 pages
Edition 1st Edition
Arrow right icon
Toc

Table of Contents (19) Chapters Close

Oracle Data Guard 11gR2 Administration Beginner's Guide
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Pop Quiz Answers
1. Getting Started FREE CHAPTER 2. Configuring the Oracle Data Guard Physical Standby Database 3. Configuring Oracle Data Guard Logical Standby Database 4. Oracle Data Guard Broker 5. Data Guard Protection Modes 6. Data Guard Role Transitions 7. Active Data Guard, Snapshot Standby, and Advanced Techniques 8. Integrating Data Guard with the Complete Oracle Environment 9. Data Guard Configuration Patching 10. Common Data Guard Issues 11. Data Guard Best Practices Index

Time for action – verifying synchronization between the primary and standby databases


By using the following steps, you can control whether the standby database is synchronized with primary:

  1. On the standby database, query the V$ARCHIVED_LOG view for the archived and applied sequences.

    For the last archived sequence, use the following:

    SQL> SELECT MAX(SEQUENCE#) FROM V$ARCHIVED_LOG;
    MAX(SEQUENCE#)
    --------------
               145
    

    For the last applied sequence, use the following:

    SQL> SELECT MAX(SEQUENCE#) FROM V$ARCHIVED_LOG WHERE APPLIED='YES';
    MAX(SEQUENCE#)
    --------------
               144
    

    From the preceding two queries, we see that the latest sequence, 145, is being archived or written into the standby redo logfiles. There's expected to be a lag of one sequence between archived and applied columns.

  2. Check the status of the latest log sequence.

    SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
    
     SEQUENCE# APPLIED
    ---------- ---------
           140 YES
           141 YES
      ...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image